I have an Asp.Net-MVC application consisting of several modules. Each module is implemented as a separate project. I use the following folder structure so that my files are copied to the areas folder of my main application.
<files>
<file src="Views\*.*" target=".\content\Areas\Home\Views\Home\" />
<file src="Views\Shared\*.*" target=".\content\Areas\Home\Views\Shared\" />
<file src="Controllers\*.*" target=".\content\Areas\Home\Controllers\" />
<file src="Models\*.*" target=".\content\Areas\Home\Models\" />
<file src="*AreaRegistration.cs" target=".\content\Areas\Home\" />
</files>
The following post-build event ensures that the “module” is wrapped in a nuget package and places it in a local folder in which all nuget packages for my modules will be removed.
cd $(ProjectDir)
nuget pack -OutputDirectory $(SolutionDir)ModulePackageSource\
The manifest uses the assembly-version version ($ version $ variable, which is "1.0. *") As the version for the package. So far so good, but I was wondering if there is a better way to do this?
- (, ), , post-build , nuget "ModulePackageSource" ( -). ( "ModulePackageSource" ), .
cd $(ProjectDir)
nuget update packages.config -Source $(SolutionDir)ModulePackageSource\ -FileConflictAction Ignore -NonInteractive
, nuget- ( "" ), , ( ).
:
= >
= > TFS
= > (GetLatestVersion) , ( ).
, , , ?