NUnitLite package always installs both Program.cs and Program.vb

[ChrisMaddock]

The NUnitLite package has an install script which looks like it should be delete either of these files if they do not match the project type. It doesn't seem to be working. Haven't really looked in to why, yet.

[CharliePoole]

I can verify that it worked at one time.

[ChrisMaddock]

Update: I believe install.ps1 is no longer ran at all for PackageReference or project.json NuGet scenarios.

We probably need to find a different solution for this functionality.

dotnet/ef6#189 (comment)

[ChrisMaddock]

The contentfiles can be specified with a target language in the directory - although I don't know how backwards compatible that is. Given this has been 'not working' since this time last year though, maybe not worth worrying about too much. 😄

https://docs.microsoft.com/en-us/nuget/schema/nuspec#package-folder-structure

[CharliePoole]

@ChrisMaddock From the docs, it's not clear whether installing the package would cause the files to be copied only to the corresponding project type. Experiment if you like. 😄

We also have had some discussion that indicates this causes problems when the package is installed in CI, if the user already provided their own entry point, so we may want to rethink this. Maybe it should just be provided as a sample or not provided at all.

[rprouse]

We can drop the install.ps1 and just put the files in Content and they will be copied in. If they already exist in a user's project, they will be prompted if they want to overwrite when they install or upgrade the package. It is never copied in a restore.

[CharliePoole]

@rprouse The problem isn't with overwriting a file but with having two files in the project that define Main. Whoever works on this should ensure that it works in that situation.