Vista Home Premium and VS2008, MSDN Vista 64-bit ISO - a couple questions [modified]
-
I know this has been discussed, but I don't remember the details, and I'm too lazy to search the forum. :) I recently purchased a new laptop with Vista Home Premium installed. 64 bit, no less. I should have known better. I installed my various progs, like VS2008. A few ugly things began to manifest. First, where's the menubar in Explorer? I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options. Then, one of my apps that interfaces with Visio now crashes. It works fine on 32-bit Vista Business. I'm hoping that it's not an issue with 64-bit Vista. But the real kicker was when I tried to debug the app, which is a mix of managed (C#) and unmanaged (C++) code. I dutifully selected the "debug into unmanaged code" option in VS2008, fired up the debugger, and was told that I can't debug unmanaged code on the "current platform". So, I decided to follow the advice others have often repeated--the first thing they do on getting a new machine is wipe it clean and install the OS without any of the other crap that comes with it (I did make recovery disks first). So, the first question is, is Vista Home Premium so lame? The next question is, I downloaded from MSDN the Vista-64 bit OS ISO. It says it includes Home, Business, etc, all the way up to Ultimate. But nowhere during the installation process does it even ask me what version of the OS I want to install. Why is this? Is the OS version tied to the key? [edit] Interesting, it installed Vista Ultimate[/edit] Marc
Thyme In The Country Interacx My Blog
modified on Tuesday, September 23, 2008 9:09 AM
We have Home Premium and Ultimate machines here (both 32 and 64 bit) and I've never had a problem with mixed mode debugging in VS2008 in any of them. Ditto for Win2k8 x64 (which is on my main dev box).
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
I know this has been discussed, but I don't remember the details, and I'm too lazy to search the forum. :) I recently purchased a new laptop with Vista Home Premium installed. 64 bit, no less. I should have known better. I installed my various progs, like VS2008. A few ugly things began to manifest. First, where's the menubar in Explorer? I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options. Then, one of my apps that interfaces with Visio now crashes. It works fine on 32-bit Vista Business. I'm hoping that it's not an issue with 64-bit Vista. But the real kicker was when I tried to debug the app, which is a mix of managed (C#) and unmanaged (C++) code. I dutifully selected the "debug into unmanaged code" option in VS2008, fired up the debugger, and was told that I can't debug unmanaged code on the "current platform". So, I decided to follow the advice others have often repeated--the first thing they do on getting a new machine is wipe it clean and install the OS without any of the other crap that comes with it (I did make recovery disks first). So, the first question is, is Vista Home Premium so lame? The next question is, I downloaded from MSDN the Vista-64 bit OS ISO. It says it includes Home, Business, etc, all the way up to Ultimate. But nowhere during the installation process does it even ask me what version of the OS I want to install. Why is this? Is the OS version tied to the key? [edit] Interesting, it installed Vista Ultimate[/edit] Marc
Thyme In The Country Interacx My Blog
modified on Tuesday, September 23, 2008 9:09 AM
Marc Clifton wrote:
where's the menubar in Explorer
Organize / Layout / Menu Bar
Marc Clifton wrote:
display options
Organize / Folder and Search Options As for the whole problem with your code dying it's probably because .NET 2.0 will by default try to run in native x64 mode and your code is trying to mix with code compiled for 32bit mode (Visio and I'm assuming your c++ code.) To change this you will need to create a new build target under your C# project for 32bit and things should run fine then.
Gavin Taylor
-
I know this has been discussed, but I don't remember the details, and I'm too lazy to search the forum. :) I recently purchased a new laptop with Vista Home Premium installed. 64 bit, no less. I should have known better. I installed my various progs, like VS2008. A few ugly things began to manifest. First, where's the menubar in Explorer? I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options. Then, one of my apps that interfaces with Visio now crashes. It works fine on 32-bit Vista Business. I'm hoping that it's not an issue with 64-bit Vista. But the real kicker was when I tried to debug the app, which is a mix of managed (C#) and unmanaged (C++) code. I dutifully selected the "debug into unmanaged code" option in VS2008, fired up the debugger, and was told that I can't debug unmanaged code on the "current platform". So, I decided to follow the advice others have often repeated--the first thing they do on getting a new machine is wipe it clean and install the OS without any of the other crap that comes with it (I did make recovery disks first). So, the first question is, is Vista Home Premium so lame? The next question is, I downloaded from MSDN the Vista-64 bit OS ISO. It says it includes Home, Business, etc, all the way up to Ultimate. But nowhere during the installation process does it even ask me what version of the OS I want to install. Why is this? Is the OS version tied to the key? [edit] Interesting, it installed Vista Ultimate[/edit] Marc
Thyme In The Country Interacx My Blog
modified on Tuesday, September 23, 2008 9:09 AM
Marc Clifton wrote:
I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options.
Alt+T in an explorer window will bring up the tools menu just like every other version of windows. From there you can select Folder Options followed by selecting the View tab. Now configure as required. If you want to disable the 'intelligent' folder type selection you can follow this guide: http://www.tweakguides.com/VA_4.html[^]
-
I know this has been discussed, but I don't remember the details, and I'm too lazy to search the forum. :) I recently purchased a new laptop with Vista Home Premium installed. 64 bit, no less. I should have known better. I installed my various progs, like VS2008. A few ugly things began to manifest. First, where's the menubar in Explorer? I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options. Then, one of my apps that interfaces with Visio now crashes. It works fine on 32-bit Vista Business. I'm hoping that it's not an issue with 64-bit Vista. But the real kicker was when I tried to debug the app, which is a mix of managed (C#) and unmanaged (C++) code. I dutifully selected the "debug into unmanaged code" option in VS2008, fired up the debugger, and was told that I can't debug unmanaged code on the "current platform". So, I decided to follow the advice others have often repeated--the first thing they do on getting a new machine is wipe it clean and install the OS without any of the other crap that comes with it (I did make recovery disks first). So, the first question is, is Vista Home Premium so lame? The next question is, I downloaded from MSDN the Vista-64 bit OS ISO. It says it includes Home, Business, etc, all the way up to Ultimate. But nowhere during the installation process does it even ask me what version of the OS I want to install. Why is this? Is the OS version tied to the key? [edit] Interesting, it installed Vista Ultimate[/edit] Marc
Thyme In The Country Interacx My Blog
modified on Tuesday, September 23, 2008 9:09 AM
Marc Clifton wrote:
Is the OS version tied to the key?
Yes. There're only two vista disk images. 32 and 64 bit. All else is driven by the key you use. IF you only have one disk, you can order the second from MS for a nominal fee, IIRC $10.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
Marc Clifton wrote:
where's the menubar in Explorer
Organize / Layout / Menu Bar
Marc Clifton wrote:
display options
Organize / Folder and Search Options As for the whole problem with your code dying it's probably because .NET 2.0 will by default try to run in native x64 mode and your code is trying to mix with code compiled for 32bit mode (Visio and I'm assuming your c++ code.) To change this you will need to create a new build target under your C# project for 32bit and things should run fine then.
Gavin Taylor
Gavin Taylor wrote:
Organize / Layout / Menu Bar
Gads. How the heck am I going to remember that a year from now when I encounter this again, most likely.
Gavin Taylor wrote:
To change this you will need to create a new build target under your C# project for 32bit and things should run fine then.
Awesome! Thanks! Marc
-
We have Home Premium and Ultimate machines here (both 32 and 64 bit) and I've never had a problem with mixed mode debugging in VS2008 in any of them. Ditto for Win2k8 x64 (which is on my main dev box).
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
Anna-Jayne Metcalfe wrote:
We have Home Premium and Ultimate machines here (both 32 and 64 bit) and I've never had a problem with mixed mode debugging in VS2008 in any of them. Ditto for Win2k8 x64 (which is on my main dev box).
Thanks Anna! That gives me some confidence that it's me, not Vista. :) Marc
-
Anna-Jayne Metcalfe wrote:
We have Home Premium and Ultimate machines here (both 32 and 64 bit) and I've never had a problem with mixed mode debugging in VS2008 in any of them. Ditto for Win2k8 x64 (which is on my main dev box).
Thanks Anna! That gives me some confidence that it's me, not Vista. :) Marc
Anytime Marc. :)
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
I know this has been discussed, but I don't remember the details, and I'm too lazy to search the forum. :) I recently purchased a new laptop with Vista Home Premium installed. 64 bit, no less. I should have known better. I installed my various progs, like VS2008. A few ugly things began to manifest. First, where's the menubar in Explorer? I want to be able to show the filename extensions as part of the filename, but there's no way I can see to set the display options. Then, one of my apps that interfaces with Visio now crashes. It works fine on 32-bit Vista Business. I'm hoping that it's not an issue with 64-bit Vista. But the real kicker was when I tried to debug the app, which is a mix of managed (C#) and unmanaged (C++) code. I dutifully selected the "debug into unmanaged code" option in VS2008, fired up the debugger, and was told that I can't debug unmanaged code on the "current platform". So, I decided to follow the advice others have often repeated--the first thing they do on getting a new machine is wipe it clean and install the OS without any of the other crap that comes with it (I did make recovery disks first). So, the first question is, is Vista Home Premium so lame? The next question is, I downloaded from MSDN the Vista-64 bit OS ISO. It says it includes Home, Business, etc, all the way up to Ultimate. But nowhere during the installation process does it even ask me what version of the OS I want to install. Why is this? Is the OS version tied to the key? [edit] Interesting, it installed Vista Ultimate[/edit] Marc
Thyme In The Country Interacx My Blog
modified on Tuesday, September 23, 2008 9:09 AM
Marc Clifton wrote:
where's the menubar
"They" removed it because it "gives too much power to the user" most likely. It's not only in explorer, almost every new MS program has its "power user options" (such as opening the Folder Options dialog) well hidden "to prevent accidental- or misuse" Being able to see/change file extensions is apparently "deemed hazardous"
-
Gavin Taylor wrote:
Organize / Layout / Menu Bar
Gads. How the heck am I going to remember that a year from now when I encounter this again, most likely.
Gavin Taylor wrote:
To change this you will need to create a new build target under your C# project for 32bit and things should run fine then.
Awesome! Thanks! Marc
Debugging doesn't work well in a 64-bit build - or an "Any CPU" build on a 64-bit system, which is equivalent. I've eventually settled on using Configuration Manager to change the Platform of each project to x86 for Debug / Any CPU. That way you can just select Debug or Release and not have to change the active solution platform as well. HTH, Nick
---------------------------------- Be excellent to each other :)
-
Marc Clifton wrote:
Is the OS version tied to the key?
Yes... ;)
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
As an elaboration, the MSDN disc (and the one they gave away for free at the Heroes Happen Here thing earlier in the year) contains the full Vista package. It uses your license key to determine which parts of that package (Home Basic/Premium, Business, Ultimate, etc.) to enable when you install. That's why they let you put off entering the license key until after you've finished installing the OS.
Imagine that you are hired to build a bridge over a river which gets slightly wider every day; sometimes it shrinks but nobody can predict when. Your client provides no concrete or steel, only timber and cut stone (but they won't tell you what kind). The coefficient of gravity changes randomly from hour to hour, as does the viscosity of air. Your only tools are a hacksaw, a chainsaw, a rubber mallet, and a length of rope. Welcome to my world. -Me explaining my job to an engineer