-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jm update docs for net standard #137
Conversation
…nd fix places where examples used the old namespace structure.
Now, launch Visual Studio and open `Keen.sln`. Build the solution, discover unit tests, and run them. Or, if using the .NET Core SDK tools, build and make sure tests pass: | ||
|
||
```ssh | ||
$ dotnet build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this actually work these days from the root of the project?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it will, but I should probably mention error MSB3644
or explicitly passing -f netstandard2.0
on platforms where you don't/can't have the right SDK/targeting pack for netfx4.5.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fun fact: running dotnet test
from the root of the solution works too, which I didn't realize.
- Call out an error/warning that occurs building the 4.5 target on non-Windows platforms. - I noticed the NewSemVer script is trying to clean the `Debug` config instead of `Release`. - There were some lingering references to the old `netfx` config in the .csproj files.
No description provided.