VS8 on Vista [modified]
-
Am I the only person not having problems installing VS on Vista? Admitedly I have the VMs but ended up not using them, I managed to get 2003.Net, 2005 and 2008 installed on Vista U64 with only minor problems.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
VS on Vista is running fine for me - no problems at all. I have to say that I find Vista to be sweet as a nut - not on a par with Windows 2003, but definitely better than XP.
Deja View - the feeling that you've seen this post before.
-
You should tell your roommate to lay off the weed. Save it for weekends, not Mondays! :)
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
Am I the only person not having problems installing VS on Vista? Admitedly I have the VMs but ended up not using them, I managed to get 2003.Net, 2005 and 2008 installed on Vista U64 with only minor problems.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
My only, probably unrelated, problem is missing Intellisense for XAML, on 2008 on Vista. No idea what caused it, but nothing brings it back. I run 2005 and 2008 at work, and 2008 at home, on my little Celeron 1.6GHz laptop with 1.25GB ram, no problems.
-
I am running VS2005 and VS2008 on vista machines with relatively no problems. The only issue that I have run accross is in my COM development. If I want visual studio to auto register my components after I compile I have to run VS as an administrator.
I now always have to run 2008 as admin at work, or it just crashes on startup. I'm sure it's not a Vista issue, and suspect third party code to be responsible.
-
My only, probably unrelated, problem is missing Intellisense for XAML, on 2008 on Vista. No idea what caused it, but nothing brings it back. I run 2005 and 2008 at work, and 2008 at home, on my little Celeron 1.6GHz laptop with 1.25GB ram, no problems.
-
My roommate just mentioned that he heard that Visual Studio 8 gets around Vista problems by installing an XP Virtual Machine. Does anybody know if there's any truth to this? Edit: Maybe I should clarify: I'm not asking whether programming in Vista is a good idea - I know it's not. I'm asking whether anyone knows anything about the underlying architecture of VS8 on Vista, one way or the other. Does anybody actually use VS8 on Vista who would know for sure?
modified on Monday, May 5, 2008 1:37 PM
-
I now always have to run 2008 as admin at work, or it just crashes on startup. I'm sure it's not a Vista issue, and suspect third party code to be responsible.
I wasnt having any troubles with VS2005 or 2008 until I installed VSS2005 and now VS2005 randomly crashes with an error not implemented or always shows this error when checking in or out but doesnt crash and completes the operation. This happens on my desktop but my laptop runs sweet as a nut. Took some getting used to but I dont dislike Vista.
At university studying Software Engineering - if i say this line to girls i find they won't talk to me Dan
-
My roommate just mentioned that he heard that Visual Studio 8 gets around Vista problems by installing an XP Virtual Machine. Does anybody know if there's any truth to this? Edit: Maybe I should clarify: I'm not asking whether programming in Vista is a good idea - I know it's not. I'm asking whether anyone knows anything about the underlying architecture of VS8 on Vista, one way or the other. Does anybody actually use VS8 on Vista who would know for sure?
modified on Monday, May 5, 2008 1:37 PM
Trevortni wrote:
I'm not asking whether programming in Vista is a good idea - I know it's not.
Why? Don't just make a statement like that without putting in your tale of woe and battle scars gained.
Deja View - the feeling that you've seen this post before.
-
Trevortni wrote:
I'm not asking whether programming in Vista is a good idea - I know it's not.
Why? Don't just make a statement like that without putting in your tale of woe and battle scars gained.
Deja View - the feeling that you've seen this post before.
Why? Because before I put that in there, all I was getting was responses telling me not to program in Vista. I was just trying to reiterate that I don't care about the advisability of using Vista, in an attempt to reduce responses that don't answer my question. So now I'm getting a whole lot of other responses that don't answer my question in completely different ways. :)
-
Why? Because before I put that in there, all I was getting was responses telling me not to program in Vista. I was just trying to reiterate that I don't care about the advisability of using Vista, in an attempt to reduce responses that don't answer my question. So now I'm getting a whole lot of other responses that don't answer my question in completely different ways. :)
Reading the responses, I believe your question has been answered - VS2008 doesn't run in an XP VM on Vista. It's been coded to work *ahem* properly in Vista.
Deja View - the feeling that you've seen this post before.
-
My roommate just mentioned that he heard that Visual Studio 8 gets around Vista problems by installing an XP Virtual Machine. Does anybody know if there's any truth to this? Edit: Maybe I should clarify: I'm not asking whether programming in Vista is a good idea - I know it's not. I'm asking whether anyone knows anything about the underlying architecture of VS8 on Vista, one way or the other. Does anybody actually use VS8 on Vista who would know for sure?
modified on Monday, May 5, 2008 1:37 PM
When you say VS8 you mean Visual Studio 2005 right? From my experience VS8 and VS9 (2005 and 2008) work fine under Vista 32 bits, and also Vista 64 bits.
Trevortni wrote:
whether programming in Vista is a good idea - I know it's not
So rather than blindly believing the negative buzz about vista you should see for yourself, and try it out.
-
Reading the responses, I believe your question has been answered - VS2008 doesn't run in an XP VM on Vista. It's been coded to work *ahem* properly in Vista.
Deja View - the feeling that you've seen this post before.
No, actually, my question hasn't even been addressed. I'm asking if VS2008 runs "properly" in Vista because it's actually running on it's own XP VM. All people are saying is that it runs on Vista - which I knew before I posted - and nobody's bothering to even address the question of architecture.
-
No, actually, my question hasn't even been addressed. I'm asking if VS2008 runs "properly" in Vista because it's actually running on it's own XP VM. All people are saying is that it runs on Vista - which I knew before I posted - and nobody's bothering to even address the question of architecture.
Sorry, but perhaps I wasn't making myself clear when I said that it didn't run in an XP VM, and that it ran properly. How can I put it plainly - it is not running in a VM - it's running directly on the OS (Vista). There's only so many ways that I can say this.
Deja View - the feeling that you've seen this post before.
-
When you say VS8 you mean Visual Studio 2005 right? From my experience VS8 and VS9 (2005 and 2008) work fine under Vista 32 bits, and also Vista 64 bits.
Trevortni wrote:
whether programming in Vista is a good idea - I know it's not
So rather than blindly believing the negative buzz about vista you should see for yourself, and try it out.
Blindly believing negative buzz? I am the person primarily in charge of Vista compatibility at my company. I HATE VISTA. And I think I have good reason to. Stop assuming, before I'm forced to pull out the ultimate forum weapon: name-calling. :-) As for VS2008, you are still missing the point, like (almost) every single other person who has responded to the question. I don't care how well VS2008 works under Vista, I'm wondering whether the underlying method for how it works with Vista is by using a VM, like my friend heard. Does anybody know?
-
Sorry, but perhaps I wasn't making myself clear when I said that it didn't run in an XP VM, and that it ran properly. How can I put it plainly - it is not running in a VM - it's running directly on the OS (Vista). There's only so many ways that I can say this.
Deja View - the feeling that you've seen this post before.
-
Sorry, I thought you were summing up all the other people that said it works *somehow* on Vista, without the user needing to manually use a VM. But you're actually telling me that VS2008 does not internally use a VM to work with Vista?
Trevortni wrote:
But you're actually telling me that VS2008 does not internally use a VM to work with Vista?
Correct.
Deja View - the feeling that you've seen this post before.
-
Blindly believing negative buzz? I am the person primarily in charge of Vista compatibility at my company. I HATE VISTA. And I think I have good reason to. Stop assuming, before I'm forced to pull out the ultimate forum weapon: name-calling. :-) As for VS2008, you are still missing the point, like (almost) every single other person who has responded to the question. I don't care how well VS2008 works under Vista, I'm wondering whether the underlying method for how it works with Vista is by using a VM, like my friend heard. Does anybody know?
Trevortni wrote:
And I think I have good reason t
Well it would be interesting to hear about the specific reasons that make you feel this way. I am not assuming more than I can read in your posts, so please elaborate so I can know you are not like the people who just follow the buzz.
Trevortni wrote:
you are still missing the point
Are you sure? VS8 is VS 2005, and Vista did not exist when it was released. So.... (This is why I was doing the clarification about VS8 and VS9)
Trevortni wrote:
name-calling
Please spare us this.
Trevortni wrote:
I HATE VISTA
So strong feelings for an OS? Be careful you're about to fall in love :)
-
Trevortni wrote:
And I think I have good reason t
Well it would be interesting to hear about the specific reasons that make you feel this way. I am not assuming more than I can read in your posts, so please elaborate so I can know you are not like the people who just follow the buzz.
Trevortni wrote:
you are still missing the point
Are you sure? VS8 is VS 2005, and Vista did not exist when it was released. So.... (This is why I was doing the clarification about VS8 and VS9)
Trevortni wrote:
name-calling
Please spare us this.
Trevortni wrote:
I HATE VISTA
So strong feelings for an OS? Be careful you're about to fall in love :)
Specific Reason: Virtualization Microsoft, pre-Vista: "All program data is to be stored in the appropriate sub-folder of Program Files. System-wide registry information for your programs should be kept in HKLM." Microsoft, post-Vista: "Too many programmers are putting program data in Program Files! This is a deplorable, and a horrible security risk! We've got to stop developers from putting data in such an obvious location! Ditto on HKLM! But it's okay - we'll be super nice to the poor backwards developers who still program using the recommended practices that are so last week, and we'll virtualize, so instead of their programs revealing that we're doing something sneaky, their programs will think they're connecting to (their own!) data, but it will break somewhere else down in a related program that their software is designed to work with without any immediate indication of what's going on, or where their data has disappeared to!" Granted, there are two simple ways to circumvent this. The first, and most obvious, is to turn off UAC. Of course, if you're writing a program that interfaces with certain software, such as QuickBooks, this is not an option, as QuickBooks won't allow you to access QuickBooks without UAC on, and both QB and your program non-elevated. Also, relying on your user to turn off UAC is a bad idea. The second way is to change folder security settings. This took several weeks to get working, thanks to a lot of things that I'm really too tired right now to go into, and this is a really more cumbersome than it needs to be. Why can't M$ at least let a program access the folder it's installed in? ....My brain's getting frazzled. No more Vista talk from me, now that someone has finally answered my question. It's just that, overall, my Vista experience has been anything but pleasant. Sorry for snapping at you earlier.
-
Trevortni wrote:
But you're actually telling me that VS2008 does not internally use a VM to work with Vista?
Correct.
Deja View - the feeling that you've seen this post before.