You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,22 @@ Make sure that the `TinCan/Properties/AssemblyInfo.cs` has been updated with new
2
2
3
3
TinCan -> Properties -> Assembly Information
4
4
5
-
Then set the Build Configuration to "Release" and build the solution. (Verify `bin/Release/TinCan.dll` has correct version.)
5
+
Obtain the `TinCan.NET.pfx` file that is used for signing the relevant portions of the release.
6
+
7
+
Then right-click the solution in the "Solution Explorer" view and select "Batch Build...". Check the "Build" checkbox for the following `TinCan` configurations:
8
+
Release-net35
9
+
Release-net40
10
+
Release-net45
11
+
Release-net45-signed
12
+
13
+
Then click "Build" to build the selected configurations. (Verify `bin/Release/net<X>/TinCan.dll` has correct version.)
Note: Providing a `Configuration` property is mandatory, otherwise `nuget` will build the `Debug` configuration and include that in the package. The `<files>` portion of the `.nuspec` ensures all releases built previously are in the created `nuget` package.
22
+
13
23
Commit the updated assembly information file and push to master. Upload the generated `TinCan.(version).nupkg` as a GitHub tag release.
0 commit comments