Permissions for VB.Net2005

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
when programming with VB.Net2005 you quite often need to have more
privileges than the normal office user. In the past, this hasn't been too
much of an issue as I have a user with full admin privileges that I use just
for that. Understandably, I cannot use that login to access the Web.

With Visual Studio becoming more integrated with the Web, can anyone suggest
what privileges I really need to be able to create Windows and Web projects
whilst also being able to persuade our systems manager to allow me access to
the on line content too.

Thanks
 
Hello John,

Welcome to the MSDN newsgroup.

From your description, I understand you're developing some .net based
applications on a restricted shared machine. You used to develop
applications under a local admin account on that machine and it works well.
However, when you try developing some web application, it fails, correct?
If there is anything I misunderstand, please feel free to post here.

As for developing .net application through Visual Studio, generally
speaking, we can perform basic development tasks under a non-admin account.
And that account should be granted some basic permissions, such as the "Vs
Developers" group or "Debugger Users" group.

For web application development, do you mean the ASP.NET web application
development? If so, Visual Studio(include VB.NET 2005) include two ASP.NET
web application development model, through IIS(also supported in vs 2003)
or through the Test WebServer shipped with .net framework 2.0. So are you
developing the web applciation through IIS or the test webserver(file
system based web project)? Based on my experience, most people will
encounter some permission issue when try debugging an ASP.NET application
under a non-admin account, this is because a .net application running under
a certain account(suppose it is userA) can only be debugged by that very
account(userA) rather than any other accounts. And by default ASP.NET
hosted in IIS is running under IIS process account(different from our logon
user account), that'll cause some problems in such scenario.

Here is a good MSDN article which introduces some common permission issue
and best practice on developing in Visual Studio IDE under non-Admin
account:

#Developing Software in Visual Studio .NET with Non-Administrative
Privileges
http://msdn.microsoft.com/library/en-us/dv_vstechart/html/tchdevelopingsoftw
areinvisualstudionetwithnon-administrativeprivileges.asp?frame=true

In addition, if your problem is a particular case, would you provide some
decent error info when you encountering the issue?

Hope this helps some.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hello John,

Haven't heard from you, how are you doing on this issue? Have you got any
progress or does my last reply helps you a little? If there is still
anything we can help you, please feel free to post here.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Steven,

Been out of the office for a couple of days so only just picked up your reply.

You slightly misunderstood my question although having said that your
posting was of use. I'm going to have a look at the article you mentioned.

Basically, although we know we shouldn't, we tend to always develop using an
account with Domain Administrators privieges. This first came about in an
earlier version of VB when half the options were missing from the menus if
you used an ordinary user account. You also needed the admin privileges to
install VB as the installation needed to write to the registry which our
ordinary users can't do.

As you say there are issues in relation to ASP and also, I think, when
accessing Web services that mean it is easier to simply use the Admin user
most of the time.

I guess that one of our problems is that we aren't full time programmers.
While we do develop our own code, we also get involved with purchasing
systems etc so never seem to have time to sit down and become completely up
to date with the new versions of VB as they are released. Personally, I have
enough problems just writing bug free code without the additional worry of
security causing problems.

I'll let you know how things are going when I've read the article.
 
Hi John,

Glad to hear from you. I'm sorry for the misunderstanding in my first
response. Anyway, please feel free to let me know your main concerns after
you read that article, we'll try best to help you find the information you
want.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hello John,

Have you had a chance to evaluate the information in that article or have
you got any progress on this issue? As always, if you have any further
questions or anything we can help, please don't hesitate to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
 
Back
Top