M
Mo0t
Guest
Hello,
I am fairly new to Development in Visual Studio, So chances are i have made some rookie errors.
I have recently been working on a solution with several projects nested inside of it. the solution Contains an ASP.NET MVC WEB API site as well as a client windows service (with an installer generated via the Microsoft Visual Studio Installer Projects extension) and a class library, for sharing code between the previously mentioned projects.
I have been backing the solution up to TFS as i go, so when i found out that i needed to switch PC's, I figured, no big deal, i will just jump on the new PC and pull the project down from TFS.
However, after installing visual studio and getting latest, the first thing that i noticed was that only my web application was visible in the project. To resolve this i started to "Add existing project" and importing the existing projects from their nested sub-folders.
I could not load the project for the installer, as i did not have the extension loaded, so i loaded this manually first.
I now have a whole bunch (130) errors to resolve and a whole bunch of warnings on various references etc, And although my nuget packages were included in a "packages" sub-folder, they did not seem to import correctly. I added this sub-folder as a Package source inside the nuget options although i'm not sure yet if i need to go through and re-add each package to the project for it to work correctly.
At this point it seems that i have obviously structured my project in entirely the wrong way.
Can anyone offer me any advice/pro tips on how to setup this project (and future projects) so that:
Set themselves up/ work for anyone who gets latest on a new PC?
What am i missing and/or what have i done wrong?
Thanks in advance for helping!
Continue reading...
I am fairly new to Development in Visual Studio, So chances are i have made some rookie errors.
I have recently been working on a solution with several projects nested inside of it. the solution Contains an ASP.NET MVC WEB API site as well as a client windows service (with an installer generated via the Microsoft Visual Studio Installer Projects extension) and a class library, for sharing code between the previously mentioned projects.
I have been backing the solution up to TFS as i go, so when i found out that i needed to switch PC's, I figured, no big deal, i will just jump on the new PC and pull the project down from TFS.
However, after installing visual studio and getting latest, the first thing that i noticed was that only my web application was visible in the project. To resolve this i started to "Add existing project" and importing the existing projects from their nested sub-folders.
I could not load the project for the installer, as i did not have the extension loaded, so i loaded this manually first.
I now have a whole bunch (130) errors to resolve and a whole bunch of warnings on various references etc, And although my nuget packages were included in a "packages" sub-folder, they did not seem to import correctly. I added this sub-folder as a Package source inside the nuget options although i'm not sure yet if i need to go through and re-add each package to the project for it to work correctly.
At this point it seems that i have obviously structured my project in entirely the wrong way.
Can anyone offer me any advice/pro tips on how to setup this project (and future projects) so that:
- sub-projects
- dependancies
- nuget packages
- extensions
Set themselves up/ work for anyone who gets latest on a new PC?
What am i missing and/or what have i done wrong?
Thanks in advance for helping!
Continue reading...