Open michaelaird opened 7 years ago
Thanks for the heads up - I've voted
Do you think compiling the Script# mscrolib to a greater version than 4.0 would work around this issue?
Possibly. That might work for individuals who are willing to do their own builds but given this project has essentially been "done" for several years, I think it's unlikely that an updated package will be released. (As an aside, we've been migrating our Script# to TypeScript using the excellent Rosetta project)
Do you have any info on how to get Rosetta going?
@scottdurow Let's take this offline. Email me at michael at campbrain.com and I can give you some pointers.
This should be solved as workaround was provided:
This can probably be resolved by setting the following property in the MSBuild project file:
<DisableHandlePackageFileConflicts>true</DisableHandlePackageFileConflicts>
@michaelaird Rosetta sounds intriguing. I tried and succeeded generating .d.ts files (after removing some empty namespace attributes [ScriptNamespace("")]
). Could you look into https://github.com/scottdurow/SparkleXrm/issues/452 and provide some feedback please?
FYI:
It looks like the latest preview build of VS 2017 breaks Script# compilation due to mscorlib conflict resolution.
I've logged a bug here: https://developercommunity.visualstudio.com/content/problem/138986/1550-preview-2-breaks-scriptsharp-compilation.html . Please add comments and upvote there.