-
Notifications
You must be signed in to change notification settings - Fork 627
Developer Setup
As we move to support cross platform development on .NET Core all developers will need to ensure they have the proper SDK version. Existing developers who have worked with the project before will need to follow the steps below. New developers will also need to ensure they have the SDK but shouldn't have to worry about steps 4 to 6.
Steps for .NET Core version
- Download and install Visual Studio 2017 (Community, Professional or Enterprise) here
During Installation ensure the following workloads are selected
- ASP.NET and web development
- Azure development
- .NET core cross platform development
During the installation ensure the following individual components are selected
- .NET Core Runtime
- TypeScript SDK
Note: for a complete list of Visual Studio Components and Workloads see https://docs.microsoft.com/en-us/visualstudio/install/workload-and-component-ids
Note: Have you worked on the allReady app in the past? If so, this note is for you. Does the solution build fail to run? Do you see a runtime error "HTTP Error 502.5 Process Failure"? Check your local user directory C:\Users<userid> for a local already .mdf and/or .ldf; delete these files. They will be rebuilt when the app is run. If your curious about the why, debug the application from Visual Studio and you'll see the root cause in the thrown exception.
-
Open the AllReady Solution
-
Clean the solution
-
Perform a nuget package restore either through VS or if you prefer using dotnet restore
-
Build and run the application
Possible issues In some cases; things can get a bit messed up in VS and even with a clean, things are left around. If you have any problems, try a fresh clean and then navigate to the project folder and delete the obj and bin folders manually. Then run a nuget restore and rebuild the solution.
Please see Running on Linux for advice on getting set up on Linux.
Please see Running on Mac OS X for advice on getting set up on Mac.