1d602d1205
- Tied into VS4Macs ProjectExtensions in order to bootstrap our Razor world. - We currently watch all DotNet projects with the expectation that they're the only ones that can potentially turn into Razor compatible projects. - Added a fallback Razor project host which is used for pre-Razor SDK Razor versions (< 2.1). - Added a default Razor project host which consumes all MSBuild data from the users packages and sets up the Razor world accordingly. - Had to modify some existing contracts to work better with new expectations. one of these was the VS4Mac specific Workspace accessor; essentially we needed to be able to lookup a workspace from a solution. - Some of our previous expectations about addins were wrong (not being able to directly reference your libraries). To avoid using reflection to bootstrap our types I tried out directly referencing our libraries and all worked fine. - Refactored the DefaultRazorProjectHost in windows (since we had to in Mac) for testing purposes. #2081 |
||
|---|---|---|
| .. | ||
| Properties | ||
| AddinMetadata.props | ||
| Microsoft.VisualStudio.Mac.RazorAddin.csproj | ||
| RazorAddin.cs | ||
| RazorProjectExtension.cs | ||