I guess the obvious answer is “yes” as there is always notepad and command line compilation, but if you want to use Visual Studio or do anything with IIS, Message Queues, etc. then the answer quickly becomes a frustrating no! This hasn’t usually been a problem, but having just started in a new job which is just starting out in .NET I’m finding what a frustrating experience not having admin rights can be. Visual Studio (2008) has been installed so that’s one hurdle out of the way, but a trial install of Resharper needs admin rights, as does NUnit.
I see MS are trying to make things better with a non-admin version of IIS7 (called IIS Express) around the corner which needs VS2010 (another thing on the shopping list). But until the Visual Studio toolset can be installed using a non-admin account, it’s going to continue to be a frustrating experience!
As part of his fantastic ‘What is .NET standard‘ presentation at DDD12, Adam Ralph provided an amazing amount of detail in such a short amount of time. One of the most valuable points, which is completely obvious when you think about it, is how you should work with .NET standard when creating libraries. NET standard now comes in a multitude of flavours: currently 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6 and 2.0. When starting out . . .
If you’re trying to access a class library (.NET Standard) from a traditional console application (in VS2017 those can be found under ‘Windows Classic Desktop’) you will run into problems; which can feel a little strange for something that was pretty simple in VS2015 and earlier. You can add a reference to the class library project (Resharper will even volunteer to add the dependency / namespace reference if you don’t already have it). But the . . .