-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use Paket in solutions that contain Service Fabric projects (.sfproj) #2977
Comments
@forki I see you added some sfproj awareness in the commit above. Thank you. How should I leverage that? Should paket now just work? Do I need to do anything to the sfproj I have in my paketized solution? |
there is a good chance that it now "just works". But I don't use sfproj myself so I can't verify |
Thanks. I'm out today, but will verify tomorrow (PST) |
@forki should the conversion for .sfproj files not also add an import for |
I assume it should yes. Are you using latest paket? |
Well, I am on the correct version in my .paket, but perhaps somehow an older one was referenced. I'll try again. Putting together a repo for #2976 first. |
@forki This is what paket 5.130.3 does to the .sfproj:
It does not add an import for Also, note that for |
yes I it's not a dotnet (new project style) project so that is correct |
OK, good. Is there a way to get |
Description
I have a solution that is comprised of SDK projects and a Service Fabric project (
.sfproj
). I am converting these from NuGet to Paket, but it not clear to me how the.sfproj
should be converted. The.sfproj
is generated by Visual Studio when creating a Service Fabric project, and looks like this:Lines 4 -7 were added by me.
How should I change this to use Paket?
The text was updated successfully, but these errors were encountered: