New answers tagged

0

Well, obviously you can seperate them into two solutions, add another project in solution, or have them in same project. I will tell what I would. IMHO, if you want to take advantage of Sessions in IIS and/or hide authentication process within API, write angular in Visual Studio as well. VS2015 has a pretty good integration(intellisense) with angular if you ...


0

We ended up implementing the "Windows Service" scenario knowing that it would not scale but intending to build a scalable solution when we have to. With the current implementation a Web Job runs a console application that queries the DB for all notification definitions, runs appropriate queries and sends e-mails. It is easy to test (just run the console app) ...


1

Have a look in HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\NewProjectDialog where the FxVersion key will contain the default framework choice. You could change it to a higher version and find out if it's a mistake or not. Probably not. You'll get a bunch of features & fixes in any case. Here are the Release Notes for .NET Framework 4.6.1, the ...


2

Unless an option is only a name, you could also go full OO and create an IOption interface (I don't know C# but this should more or less compile): interface IOption { String optionName(); double optionPrice(); List<IOption> exclusive(); //list of options that can't be selected with with this one //etc } Then each option implements that ...


2

Test as much as possible before deployment Deployment isn't cheap. Even if the deployment is fully automated and pushed automatically from the commit it still takes time to deploy, it prevents any use of the development environment while deploying and if you deploy a broken application the development environment is stuck until things get fixed. This ...



Top 50 recent answers are included