...
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?> <configuration> <config> <add key="repositoryPath" value="packages"/> </config> <packageRestore> <add key="enabled" value="True" /> <add key="automatic" value="True" /> </packageRestore> <packageSources> <add key="nuget.org" value="https://www.nuget.org/api/v2/" /> <add key="TeamcityAuth" value="httpshttp://build.deltares.nl/httpAuth/app/nuget/v1/FeedService.svc/" /> <add key="Teamcity" value="httpshttp://build.deltares.nl/guestAuth/app/nuget/v1/FeedService.svc/" /> </packageSources> <activePackageSource> <add key="TeamcityAuth" value="httpshttp://build.deltares.nl/httpAuth/app/nuget/v1/FeedService.svc/" /> </activePackageSource> <packageSourceCredentials> <TeamcityAuth> <add key="Username" value="dscbuildserver" /> <add key="ClearTextPassword" value="[DSCBUILDSERVERPASSWORD]" /> </TeamcityAuth> </packageSourceCredentials> </configuration> |
...
You can also make a unit test project that works in Delta Shell. To do so, install the DeltaShell.TestProject
package into your test project. Take notice of the Default Project in the Package Manager Console, because you want the DeltaShell.TestProject
to be in your test project and not in your application plugin project. The package sets the output directory of your project to $(SolutionDir)\bin\$(Configuration)
The test project also adds some extra lines to App.config.These lines make sure that your unit test can find the framework and the plugins.
...
If you have received a message that a new version of the framework has been released, you can manually update your packages in your product by executing some NuGet commands via the NuGet Package Console, which can be found under Tools > NuGet package manager. Do not forget to set your package source to TeamcityAuth.
Code Block |
---|
Update-Package DeltaShell.ApplicationPlugin -Version y.y.y.yyyyy -FileConflictAction Overwrite Update-Package DeltaShell.TestProject -Version y.y.y.yyyyy Update- -FileConflictAction Overwrite Update-Package DeltaShell.Framework -Version y.y.y.yyyyy -FileConflictAction Overwrite |
This will uninstall the old version and then install the new version. You can simply commit the files that have been changed in your projects. You don't have to commit the nuget packages, because we already have auto-restore enabled.
When you are going to commit the updated package, you can verify your commit. There are a couple of files that have changed. Namely, everything that has the version number referenced in their file. So for example, all csproj
files will have updated references. Another file is the packages.config
file that belongs to the project. It will contain an updated version number as well. All files that were in the content folder of the nuget package are replaced.
Old | New | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
csproj
| csproj
| ||||||||||
packages.config
| packages.config
|
Creating an ApplicationPlugin derivative
...