Developing with Vista

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

minestrone replied

1 April 2009, 17:35
I use eclipse so it's probably not applicable but my 4 1/2 year old XP desktop provides a much more stable development environment than my 5 month old, top of the range Vista latop. Even though my desktop runs a bundle of other servers/services on the side which the latop does not.
Leave a comment:
Churchill replied

1 April 2009, 08:31
Originally posted by VectraMan View Post

Sorry I'm confused. How can the file system affect whether the OS can stop debugging a process?

If I was sure it would fix it, I'd consider using 2008. But from what I've seen 2008 doesn't change anything, other than a load of extra .NET stuff for WPF and the like which isn't relevant to me.

Sorry, my bad.
Leave a comment:
VectraMan replied

31 March 2009, 18:29
Originally posted by Churchill View Post

Nothing to do with an update. The filesystem in Vista is less tolerant to "bugs"!

Use VS2008, it'll show you where the problems are.

Failing that PM me and we'll sort something out.

Sorry I'm confused. How can the file system affect whether the OS can stop debugging a process?

If I was sure it would fix it, I'd consider using 2008. But from what I've seen 2008 doesn't change anything, other than a load of extra .NET stuff for WPF and the like which isn't relevant to me.
Leave a comment:
thunderlizard replied

30 March 2009, 20:59
Yes - I was having the same problems on my laptop. So I got a new PC with 4GB RAM and loads of spare hard disk space and it's been quick as you like since then.
Leave a comment:
Churchill replied

30 March 2009, 20:56
Nothing to do with an update. The filesystem in Vista is less tolerant to "bugs"!

Use VS2008, it'll show you where the problems are.

Failing that PM me and we'll sort something out.
Leave a comment:
VectraMan replied

30 March 2009, 20:17
Originally posted by voodooflux View Post

No problems here. Are you running VS2005 SP1 and the corresponding SP1 update for Vista?

Yes I've got that. A clean build does seem to sort things out for a while, but that takes nearly 20 minutes. Perhaps it's just the size of the thing that is the problem.
Leave a comment:
voodooflux replied

30 March 2009, 19:55
Originally posted by VectraMan View Post

Does anybody do it?

I've been using my Vista laptop with VS2005 on a fairly large C++ project, and it's pushing me over the edge. It frequently gets itself into a state where it won't stop debugging, and won't edit and continue, and then the only way out of it is to kill the devenv process (after which I have to wait 5 minutes for "updating intellisense").

Okay so VS2005 was never sparklingly solid, but I don't have the same degree of problems with XP. I'm tempted to see if I can make my laptop dual boot XP.

No problems here. Are you running VS2005 SP1 and the corresponding SP1 update for Vista?
Leave a comment:
VectraMan started a topic Developing with Vista

30 March 2009, 19:29
Developing with Vista

Does anybody do it?

I've been using my Vista laptop with VS2005 on a fairly large C++ project, and it's pushing me over the edge. It frequently gets itself into a state where it won't stop debugging, and won't edit and continue, and then the only way out of it is to kill the devenv process (after which I have to wait 5 minutes for "updating intellisense").

Okay so VS2005 was never sparklingly solid, but I don't have the same degree of problems with XP. I'm tempted to see if I can make my laptop dual boot XP.
Tags: None