.NET Framework - VS 2005 & Vista
Asked By Brent
17-Mar-07 03:59 PM
Ok i just went from XP Professional to Vista Ultimate x64 last night. I
installed vs 2005, sp1, and the update for sp1 for vista. I started up
VS2005 and still got the warning message that deals with compatability of
Vista & VS2005 which i was suprised. I would think after the update for sp1
for vista would have taken care of that but i guess not but anyways i
digress. Part of the error message and the page its linked to says you
should run VS2005 with administrative priveledges by going to the icon
properties of the VS 2005 Icon. Anways is this still true even after you run
the update for sp1 for vista or was this just the workaround before?
thanks,
Brent
IIS
(1)
XP
(1)
Vista
(1)
Part
(1)
RobinS replied...
You have to run VS2005 in administrative mode if you are running Windows
Vista. As far as I know, they haven't done anything about that, and I
haven't seen anything posted to the contrary in any of the .Net groups
recently.
Robin S.
VJ replied...
I belivie still I think regular windows app might work, just web
applications will not. Is that true?.
VJ
John Vottero replied...
You only have to run VS2005 as an administrator if you want to do things
that only an administrator can do. Like, debug a process that's running
under a different username or registering a COM object. That's not
something that Microsoft can or should fix. Non privileged users should
never be able to debug someone elses process.
I run VS2005 as a non-administrator and I rarely ever run into problems.
Even under XP, I would use a non-admin account for 99% of my work. I only
log on with an administrator account when I really need to.
Aleks Kleyn replied...
The only thing when you need to run VS2005 in admin mode is to get access to
IIS to design and debug web page. According to message you need to wait sp1
for vista (end of the year). However if you enable windows autification in
IIS you will get ability to debug.
Aleks Kleyn

Vista or Asta la Vista ? .NET Framework I ask this question to all web designers and coders alike out there. I currently work with MS XP Media Centre 2005 Edition, but have just received my new free upgrade to Vista Home premium. Now I am a little concerned it may effect some of the programmes my web design. I have heard lots of issues with programmes no longer working with vista. I need some advice either to sit tight with XP MC2005 or go with vista beacause there aint no problems ? Thanks Phil - - http: / / www.philbrighton.co.uk Web Designer Magazine Forum Moderator http: / / webdesignermag.co.uk / forum / index.php?sid = 30f008e710b30fc98e6af916c8b41571 Expression Web Designer Discussions Vista (1) XP (1) Expression Web (1) IIS (1) ASP.NET (1) MS (1) Windows Update
2K8 SP1 (version Pro at work, version Express at home) Thanks! ASP.NET Discussions Windows XP (1) Windows Vista (1) Visual Studio (1) IIS (1) Subscribe (1) GregoryBeamer (1) Rewriters (1) Cassini (1) With VS2008 SP1 (or .NET 3 to avoid having to create tons of routing rules. I have not dinked enough with IIS 7 to see if there is anything built in, but I don't remember anything blog http: / / feeds.feedburner.com / GregoryBeamer# or just read it: http: / / feeds.feedburner.com / GregoryBeamer * ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** * * ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** * iis 7.0 support .net native filters, so they work with any content type. the vs2008 dev webserver is not iis 7.0 compatiable. if you want to do iis 7.0 developent your dev box must have iis 7.0 installed (vista or server2008). then you just configure vs2008 to use iis rather
Request.QueryString("ID") <> "") Then rsContent_ _MMColParam = Request.QueryString("ID") End If %> Expression Web Designer Discussions Windows XP (1) Expression Web (1) Vista (1) ASP.NET (1) IIS (1) XP (1) MMColParam (1) Database (1) I would not import the website. I would either publish preview in the browser in E.W. Would you agree? You will need to have IIS set up on your PC to be able to preview classic asp pages. The built in test server will not run them. If IIS is in place previewing classic asp pages in EW is no different to FrontPage IIS can be installed on Win XP Pro (but not XP Home) and certain versions of Vista (not the Home or Starter
theory but in reality. Thanks Regards ADO.NET Discussions BcadnSN7f4UbwWPVnZ2dnUVZ (1) SQL Server (1) Windows XP (1) Windows Server (1) Windows Update (1) Visual Studio (1) WaitForPendingFinalizers (1) Office (1) http Hell" was quite evident there. 1. Different dll versions *prevented* your application from running in IIS. 2. Updating a dll meant manually stopping IIS, and all applications, so a single app could be updated re: !> How many versions of memory in sight forcing other applications to be swapped out. Consider that 32-bit systems (Vista or XP) can only use 3.5GB of RAM. Take away the OS footprint, a couple .NET module scope, circular references, etc). This is true in VB.NET as well (except the part about circular references). A module level reference will live for the lifetime of the application Hell" was quite evident there. ¤ ¤ 1. Different dll versions *prevented* your application from running in IIS. ¤ 2. Updating a dll meant manually stopping IIS, and all applications, so a single app could be updated Of course with #2 you
shadow cache somewhere that it could be wedged? Thanks Mark .NET COM Interop Discussions Windows XP (1) Visual Studio 2008 (1) Visual Studio 2005 (1) Windows Installer (1) Vista (1) IIS 6.0 (1) ASP.NET (1) XP (1) I think that is the kind of type initialization error that you get when NET version are you using to compile the .NET component? * I assume you're using IIS 6.0, do you have other websites configured to run in the same application pool production environment (where there have been no reported problems) Most of our development machines are XP Pro, so most developers are using single-site IIS 5. We do have one developer using Vista, so he's got IIS 6 and he's seeing the problem too. Any ideas