Publishing executables and websites with NuGet

asp.net .net packaging nuget
Garry Shutler picture Garry Shutler · Jan 18, 2012 · Viewed 7.4k times · Source

I'm looking to standardize our publishing mechanism for libraries, executables and websites.

All the documentation on the NuGet website talks about publishing libraries, tools and source files but there does not seem to be any guidance on the directory structure when publishing fully packaged executables and websites.

Is there any guidance or existing convention on this?

If I were to make something up it would look like:

exe/net40/*.*
website/net40/**/*.*

Answer

Michelle Steele picture Michelle Steele · Jan 27, 2012

We are using Octopus Deploy by Paul Stovell, an automated deployment tool which pulls from a Nuget feed and distributes your application using a central dashboard.

We also have some msbuild scripts following the conventions on his site which tell you how to build the nuget files.

Apparently, the latest version of Teamcity (EAP) can automatically package your artifacts to nuget packages and act as a NuGet server.

We have had much success using both TC and Octopus Deploy for automated build and deployment.

Related questions

In C#, what is the difference between public, private, protected, and having no access modifier?

All my college years I have been using public, and would like to know the difference between public, private, and protected? Also what does static do as opposed to having nothing?

Read More
How to Convert JSON object to Custom C# object?

Is there an easy way to populate my C# Object with the JSON object passed via AJAX? This is the JSON Object passed to C# WEBMETHOD from the page using JSON.stringify { "user": { "name": "asdf", "teamname": "b", "email": "c", "players": ["1", "2"] } } …

Read More
Invalid postback or callback argument. Event validation is enabled using '<pages enableEventValidation="true"/>'

I am getting the following error when I post back a page from the client-side. I have JavaScript code that modifies an asp:ListBox on the client side. How do we fix this? Error details below: Server Error in '/…

Read More