Visual Studio 2012–changes necessary to start doing your work

 

Disclaimer: This post does not take any company security policies into account, actions suggested are merely provided to support getting things done as a developer…having said that Knipogende emoticon

What’s the first thing you probably will encounter when (implicitly) converting an existing solutions from an older Visual studio…

Security Bedroefde emoticon

You must ensure that you can do your work….especially when converting solutions from an older Visual studio version, it’s very annoying that solution will be migrated but are not able to change properties in projects etc.

clip_image001

Example of Zen demoter…..Changing the read-only bit from solutions (e.g. downloaded sourcecode);

clip_image003

How to start you work…and increase your Zen level?

Change User Access Control

clip_image004

clip_image006

Note: Personal judgement is necessary to determine whether this should be done!

Run Visual Studio as an administrator

You can do this by changing a property in the visual studio shortcut.

clip_image008

Now you can start doing your work

 

Glimlach

Comments

Popular posts from this blog

Azure implementation guidelines

Focus and innovation - recap of the last 2 years

BizTalk Pub/sub vs Topics based routing–discussion