ToolsĪdditionally you can also put a Powershell script into a Tools folder and Visual Studio will execute that install.ps1 script. You can also use some limited templating to format some limited text expressions like project name, default namespace and class names inside of text documents. The Content folder can hold arbitrary content that's dumped into the project's root folder. NET SDK projects and while you can have the folders, they are ignored. There no longer is support for these in the new. Just keep in mind that the following sections apply only to full framework projects.
Content and Tools Folders do not work in. NuGet packages for Full Framework projects can still package Content and Tools folders. NET Core/Standard development no longer load the content. When I recently ported this libary to ASP.NET Core - I found out that I can no longer ship my Localization Admin UI via Content bundling inside of the NuGet package as the new. This still works for the full framework package:įigure 1 - Full framework packages still support Content folders that are expanded when installed West Wind Globalization's Web components include a Localization Administration UI and the UI's HTML, CSS and Script was previously shipped as Content in the old NuGet package. Nevertheless, I have one package - where having Content shipped as part of the package is very useful.
NuGet wouldn't remove content added through the package (since it can be changed).Bad package etiquette - polluting projects with extra files.There are good reasons why this change and removal happened: In classic projects and full framework projects, you could add a content folder to your NuGet package and NuGet would install that content into projects root folder. NET SDK type project format, NuGet packages no longer can deploy content into the target project.
0 kommentar(er)
