Comments (8)
I presume that this error is related to VS2015 project format (.xproj). Previous version of MSBuild's syntax (according to MSBuild docs) is
<ItemGroup Condition="'String A' == 'String B'">
<Item1>... </Item1>
<Item2>... </Item2>
</ItemGroup>
So it has to consume any children of an ItemGroup. So therefore I presume that problem is not in RT itself, but in Visual Studio and MSBuild.
Could you contact me directly, because you are doing very interesting option of RT integration? Skype: nsu_the_cjay.
from reinforced.typings.
I don't use Skype, sorry. I didn't consider that my multi-targeted DLL doesn't contain any RT attributes (since the DLL targets both .NET35 and Core 1.0, I can't easily add RT to the project) so I can't really use the Assembly approach even if this XML warning hadn't come up.
(Also it appears that RT isn't compatible with .NET35 even in a stand-alone setup -- meaning, not a multi-targeted solution. I tried creating just a .NET35 console app and the RT nuget package won't load.)
I was able to do the static class configuration and get the desired output.
However I'm willing to help if you need anything else relating to this project configuration. I'd also be happy to test any Core changes you might make, I'd prefer to use the attribute approach and output my TS files from the same project that produces the data definition DLL.
from reinforced.typings.
Well, the problem is that it is not so easy to make .NETCore version of RT. Mainly because the main feature of RT is integration within project building process. I still couldnt find extension point for embedding RT calls to .xproj build script. If you have information about how to do that - please tell me :) Will appreciate any help.
from reinforced.typings.
I would think you need the "tools" and "scripts" section of the project.json file.
https://docs.microsoft.com/en-us/dotnet/articles/core/tools/project-json
I hate to say it, but MS has announced that project.json is going away in the next VStudio, they're going back to MSBUILD for everything, so unfortunately this would be a short-lived fix. (VS2015 is version 14, they're dropping year-names, so the next one will, confusingly, be called VS15). I think JSON files are terrible for configuration, but that decision has stalled a lot of VS14 development/integration.
from reinforced.typings.
Am I right that you suggest just sit still and wait? :)
To be honest, personally I do love MSBuild and do not have any idei who could suggest .json-build configuration. Well, conf. serialization way does not matter of course, but it seems that they have significantly changed operations flow within this "brand-new" project.json.
from reinforced.typings.
Well, it might be an easy fix.
You almost certainly will have to make other changes to support Core though. Part of my project uses reflection very heavily but it only took me a few minutes to fix that. I didn't see much else in RT that looked like it would be impacted.
If it really is as simple as fixing reflection (same features are available, they just revised the API a little) and adding RT to the project.json, it may be worth updating it anyway. I know I'd appreciate it! :)
from reinforced.typings.
btw, I've just found year-old announce that project.json will not be supported in the future.
https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-to-project-json/
So all the msbuild hacks made in RT will stay valid
from reinforced.typings.
Case closed
#48
from reinforced.typings.
Related Issues (20)
- Invalid code generated when C# code inherits from generic
- v1.6.1 does not support .NET 7 HOT 23
- Invalid code generated for explicit interface member implementation
- Export public static properties of static class to enum HOT 2
- Add raw line to output file (for example to disable eslint errors) HOT 3
- Is it possible to generate union?
- RT0999: Input string was not in a correct format.
- Are SDK Projects supported? HOT 3
- MSB6006 "" exited with code -214745073
- Issue when base class is exported as interface HOT 1
- feat: Net8 support HOT 24
- <RtDisable> and <TreatWarningsAsError> not working HOT 1
- Error MSB6006: "" exited with code 1. HOT 2
- The AddImports feature should allow you to select what quotes to use
- Generated Typescript loses information about combined enum flags when using UseString
- Improved compilation of JSDOC
- JSDOC for enums
- Add a custom property to a class HOT 4
- feat: Net9 support
- Empty file generated?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from reinforced.typings.