-
Notifications
You must be signed in to change notification settings - Fork 369
Upgrade to Roslyn packages 1.0.0 rc2 #1064
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
Conversation
add a build script which creates a nuget package
use latest AssemblyReferences version
Renaming to scriptcs-engines
Update README.md
fix build script after rename and split into 3 projects
|
can we move forward with this? I have been keeping this branch up to date for over 2 months now and I see no reason for us to stay behind on this. The only issue I can see, and I want everyone to be every of is that I renamed the roslyn module to |
…w/scriptcs into feature/roslyn-engines-rc2
|
Should also fix #1095 |
|
👍 |
[WIP] - Upgrade to Roslyn packages 1.0.0 rc2
|
Rockin! On Tue, Sep 29, 2015 at 12:55 PM Filip W notifications@github.com wrote:
|


Opening the PR for visibility and potential discussions.
This PR upgrade old Roslyn CTP from September 2012 to version 1.0.0 RC2 (.NET 4.5 compatible). Also includes a VB engine. The core work was done in this repo already https://github.com/scriptcs/scriptcs-engines
Version 1.1.0-beta is .NET 4.6 only so we will have to discuss separately what to do about it.
TODO
prepackages)ILog, they don't)build.cmd(note: acceptance tests still fail)scriptcs.csharpandscriptcs.visualbasic)Questions & issues
ScriptCs.CSharp, should we keep this name or stick withScriptCs.Engine.Roslyn? Right now I renamed everything tocsharpandvisualbasicrespectively, soroslynis no longer visible anywhereNext steps
Update to Roslyn 1.1.0-beta? However, as mentioned, that's .NET 4.6 only.