- Created a new permission set
- Created a new code group
- Associated the code group with the permission set.
- Created a strong name for the simple windows app that I was working with.
- Associated the assembly with the code group
Then after doing such simple things got the following error while trying to debug
And then what next ?
Googled .
Found in the MSDN forums that there were many souls like me who had racked their brains on this.
Solution:
===========
Turn on the Terminal Services from the Control Panel->Settings->Services.
And the VB Express works like a charm as before .
Strange isnt it ? I will research more if you find why this is so. Any of you reading this can post comments on this.