Skip to content
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

Conversation

augustoproiete
Copy link
Member

  • Add new build parameter ExcelDnaAllowPackageReferenceProjectStyle to the .props file (defaults to false) to allow for displaying error when users install ExcelDna.AddIn on projects that use the PackageReference style
  • Changing the parameter to true allows the developer to bypass the error, if the wish to use PackageReference with a workaround for copying the files, etc.

@augustoproiete augustoproiete requested a review from govert June 28, 2020 22:57
@augustoproiete augustoproiete self-assigned this Jun 28, 2020
@govert
Copy link
Member

govert commented Jun 28, 2020

Which of these do you prefer for the pre-release NuGet package with this in?
1.1.0-SdkStyleProjects
1.1.0-PackageReference

@augustoproiete
Copy link
Member Author

I think 1.1.0-SdkStyleProjects might be more explicit.

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.

@govert
Copy link
Member

govert commented Jun 28, 2020

I'm confused about whether it's the Sdk-style project file, or the NuGet PackageReference that's actuall the problem.
(Or is it the NetStandard target?)

Maybe the best name is
1.1.0-NetStandard

@augustoproiete
Copy link
Member Author

@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 NetStandard is confusing because it implies support for .NET Standard - which we don't support.

@govert
Copy link
Member

govert commented Jun 28, 2020

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
1.1.0-PackageReference
maybe?

But I'll sleep on it and push the new package in the morning.

@govert govert merged commit a762017 into Excel-DNA:master Jun 28, 2020
@augustoproiete augustoproiete deleted the allow-package-reference-via-build-config branch June 28, 2020 23:17
@augustoproiete
Copy link
Member Author

install.ps1 is one of the problems... The SetDebuggerOptions also doesn't work in SDK-project style, which means no auto F5 debugging experience anymore (find the right Excel version, etc.)

Now that this one is merged, I suggest releasing v1.1.1 or v1.2.0 (RTM) and de-listing v1.1.0 from NuGet. That avoids any confusion, and gives an RTM version that allows using ExcelDna with SDK-style projects (as long as the parameter is set in the .props file)

@govert
Copy link
Member

govert commented Jun 29, 2020

Great - yes. I'll test it a bit then make a release as package v 1.1.1.

@augustoproiete
Copy link
Member Author

Awesome. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants