-
Notifications
You must be signed in to change notification settings - Fork 6
Add c sharp source #2
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
base: master
Are you sure you want to change the base?
Add c sharp source #2
Conversation
Create ReadMe.md
Conflicts: Examples/APM/ReadMe.md
…e adjustments for implementation practicalities and concerns. Goal is to serve as basis for discussion among XML Committee before committing these source files to MESA repo.
See pull request for discussion of issues on it.
…into addCSharpSource
Hi Karen, Below is the output I received from trying to build the solution. It looks like the NuGet.exe reference isn't valid, but the other projects seem to build okay.
|
Thanks, Joe. That isn't actually the error I was expecting - I was hoping the NuGet.Packager project would fetch its own latest NuGet.exe and run the project to create the MESA.KPIML NuGet package. I can check in the .exe I've been using, for now, but it would be better to make the project fetch it from NuGet. I'll try tweaking the NuGet.targets file and see if that does the trick. |
… the NuGet packaging build to work without checking in a NuGet.exe. Also added some unit tests (getting NUnit via NuGet was actually helpful in solving the packaging, too). Cleaned up the base code and flattened the _Time_Range classes. Added GitHub URL in comments in all .cs source files.
@JoeDo, I've pushed some new updates to the branch. See if it all works for you now. Thanks! |
I'm doing a bit of testing here before committing to the main MESA repo.
@Dennis-Brandl or @JoeDo, could one of you kindly try getting the Source files, and see if KPI-ML\Source\Csharp\MESA.KPIML\KPI-ML.sln builds correctly for you (other than the D:\NuGets\ reference)? Thanks!
Also, please take a look at the .EAP model file I used in Oct. 2015 to generate the original code:
These may be misunderstandings on my part, or simple issues with how the EAP->C# conversion tool works, or with naming of the references.