Dai
@pranavkm @davidebbo My backlog of RazorGenerator stuff is kinda tied to the time I spend on my work projects that use RazorGenerator and they keep getting pushed-back due to business...
> I agree. Given the limited cycles that we have to maintain this project, we can be pretty aggressive in limiting what VS versions it targets. I salute you all...
(This reply's numbered list describes my experience and troubleshooting steps with trying to build the solution (with or without this PR merged!) 1. VS2019 gives errors about the Test project...
After more headaches, I was able to get the solution to build from within VS2019 by replacing `Microsoft.VisualStudio.Sdk.BuildTasks.14.0` (version 14.9.23) with `Microsoft.VSSDK.BuildTools` (version 15.9.3039). **I assume** this means it now...
@muso31 not yet - but I **will** be resuming on this on Friday (tomorrow, within 36 hours' time). @sitecorerebelhub - You didn't seem to have any problems building and testing...
@sitecorerebelhub are you still active on GitHub, can you answer my questions re: building your changes? I'm thinking of closing this PR and pushing ahead with my own changes instead....
@sitecorerebelhub Where is the test project of yours committed? I don't see any new commits [to your RazorGenerator fork repo](https://github.com/sitecorerebelhub/RazorGenerator) in neither the [`master`](https://github.com/sitecorerebelhub/RazorGenerator/commits/master) nor [`dev`](https://github.com/sitecorerebelhub/RazorGenerator/commits/dev) branches. The only other...
> @Jehoel is there any update on sorting this at all? Absent complete and working build instructions from the OP, I'll press-ahead with work with my own changes that remove...
@cbr-camao The problem isn't the lack of tests - the problem is that I can't get the solution and projects to build due to broken VS SDK dependencies and MSBuild...
(I deleted my previous comment after I realised it was incorrect) Looking at RazorGenerator-generated views in MVC and comparing them to `RazorGenerator.Templating`, I see that it comes down the implementation...