Demis, what is the status of the ServiceStackVS extensions? After installing them into VS2K13, I’ve noticed several do not compile (MVC5, MVC & Angular, etc.). At a minimum, the paths to the retrieved NuGet packages are wrong. After using SS in the service layer for months, I’m looking at moving into the front-end with it and would like to know the preferred front-end technologies and techniques.
Fredrick Lackey:
The only examples that come to mind are from Telerik but they use a compiled wizard to target each project. If I find any that use T4 or VS scripting, I’ll let you know.
Darren Reid:
Ahh right. Any info on your workflow for the steps you take with normal templates to get your project/solution setup up and running would be useful as I’m not familiar with this setup. If I know how you get to that folder arrangement with other templates, hopefully I can work something out to ‘calculate’ the relative paths if possible.
Darren Reid:
As these templates are multi-project templates, if you can find an example with how you would incorporate another multi-project template into your project structure that works I’ll take a look.
Do you have the latest version of SSVS installed?
If you do can you post any issues about ServiceStackVS on https://github.com/ServiceStack/Issues
+Darren Reid is maintaining SSVS and is quick to respond to any issues. SSVS is still being continually developed with updates on every release, it includes a number of templates so the best one to use is largely a matter of choice/preference.
Fredrick Lackey:
Yep… pulled down about 60 minutes ago.
Darren Reid:
Hey +Fredrick Lackey Could you post any details to what you are seeing as far as not building? I’ve just ran through creating all the C# templates and they all build restore from NuGet successfully, MVC4, MVC and Angular templates included.
The packages directory is at the same level as the .sln file. Any screenshots of what you are seeing in the directories, errors, project file would be helpful.
Fredrick Lackey:
Screenshot: http://goo.gl/5R0X6L
Figured it out. Not sure if you’d consider it a bug or not. Basically, the template uses the default paths. In my scenario, I never create projects in the Solution folder but, instead, use separate Projects / Solutions folders so I can create solutions for various purposes and pull in the relevant projects. Once I accepted all of the defaults the templates compiled. Would be great, in the future, if the paths were calculated relative to the selected paths.
Darren Reid:
+Fredrick Lackey The next version of SSVS has a different way of installing the NuGet packages to ensure the latest version of SS is used when using the New/Add project wizard. This might actually solve the pathing problem for you as well. Still being worked on for next release, but if you are interested, feel free to give it a try.
https://github.com/ServiceStack/ServiceStackVS/raw/master/dist/ServiceStackVS.vsix