csproj

I'm trying to write a plugin system with .NET Core, and one of my requirements are to be able to distribute the plugin DLL along with it's dependencies to the user for install. However, I can't figure out how to include my NuGet dependencies as a build artifact and have them output to the build folder, without having to use dotnet publish as a hack. Is there some way I can specify this in the csproj? Martin Ullrich You can add this to a <PropertyGroup> inside your csproj file to enforce copying NuGet assemblies to the built output: <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies

I'm frequently adding a lot of content files (mostly images and js) to my ASP.NET project. I'm using VS publish system, and on publish, new files are not published until I include them in the project. I would like to auto include all files in specified directory. Is there a way to specify which directories should be auto-included in csproj file or anywhere else? Old thread, I know, but I found a way to do this that I keep forgetting, and on my search to find it one last time, I stumbled upon this question. The best way I've found to this is is to use the BeforeBuild target in the .csproj file.

When I add an assembly reference to a project in Visual Studio 8 the Aliases property, of that reference, is set to "global". What is this property good for and why is it set to global? MSDN tells me that this is a list of aliases for the assembly but not why I might want to use this property or why most are aliased as "global". MSDN reference This is for "extern aliases". Suppose you want to use two different types, both of which are called Foo.Bar (i.e. Bar in a namespace of Foo ). The two types will be in different assemblies (by definition) - you use the property in VS to associate an