...
For now, we can develop the framework via Framework.sln and make sure to not change the API of the framework as much. Although, when we decide that something should go, there is nothing to stop you, since the product using that functionality has pinned its version of the framework and can work along just fine.
Building and Testing Debug version of Framework
If you have changed the framework and want to test this with a product you can use the following steps to verify the change in the framework for your product:
- You have changed something in the frame.sln solution and you have build the solution succesfully
- Open the product (NGHS.sln) you want to test / debug your new framwork with
- Restore all packages for this product
- Close the solution
- remove the generated bin folder for this solution
- Open powershell
- In Powershell go to the folder where you checked out the framework
- In Powershell goto subfolder sdk (so: svn://trunk/Framework/sdk)
- Run powershell script : ./copy-framework-bin-to-product.ps1 [PRODUCTNAME] [BUILDCONFIGURATION]
- This will copy the just build dlls from the frame work in the packages folder of the product
- Like: PS D:\svn\trunk\Framework\sdk> .\copy-framework-bin-to-product.ps1 NGHS Debug
- for more help on script use:
- get-help .\copy-framework-bin-to-product.ps1
- for more examples:
- get-help .\copy-framework-bin-to-product.ps1 -examples
- for more detail:
- get-help .\copy-framework-bin-to-product.ps1 -detailed
- Open the product solution file again with visual studio
- Build your product with latest locally build framework
Warning |
---|
If you get build errors in your product like
The reference in the project of your product is probably |
Building and Testing new Framework with all products in TeamCity
NuGet Specifications
The NuGet specifications can be found in svn under trunk/Framework/sdk
. I'm not going into detail at the moment on how these specifications work. There is enough reference material on the interwebz. There are two folders in the sdk
folder. packages
and tools
. The tools
folder contains some utility functions that can be useful during the install.ps1 script that is run when the NuGet package is installed into the csproj.
...