-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Allow devs to use PackageReference if they wish (despite current limitations) #327
Allow devs to use PackageReference if they wish (despite current limitations) #327
Conversation
Which of these do you prefer for the pre-release NuGet package with this in? |
I think However, I think a pre-release is not very useful as it'll block devs from shipping RTM versions of their own libraries. I've replied to your e-mail just now. |
I'm confused about whether it's the Sdk-style project file, or the NuGet PackageReference that's actuall the problem. Maybe the best name is |
@govert It's both... Changing the old csproj to use PackageReference breaks the current build. The new SDK-style project also breaks the current build. I think the |
I guess it's the PackageReference reference that doesn't run the Install.ps1 which is our problem. The SdkStyle file just forces that. So I'm tempted to go with But I'll sleep on it and push the new package in the morning. |
Now that this one is merged, I suggest releasing |
Great - yes. I'll test it a bit then make a release as package v 1.1.1. |
Awesome. Thanks! |
ExcelDnaAllowPackageReferenceProjectStyle
to the.props
file (defaults tofalse
) to allow for displaying error when users installExcelDna.AddIn
on projects that use thePackageReference
styletrue
allows the developer to bypass the error, if the wish to usePackageReference
with a workaround for copying the files, etc.