Printable View
I couldnt find what I needed but this should be an easy question, hopefully.
I am installing VS 6 Enterprise Edition and its giving me a compatibility issue before the install ...
Seems it doesnt like C++ :(
Whats the workaround as it should be the same as it was on any beta version of Vista.
Thanks
I believe you have to run it under XP compatibility mode (Run as... etc.)
Doh! Was just thinking if I dont install C++ from VS 6 and did install it under VS 2003/2005 would it be the same or will the C++ projects require the FW?
I want C++ without the dependancy of the FW.
VC++ 2005 is a far far superior compiler to VC++ 6. It does compile both managed code (C++/CLI) and standard unmanaged C++.
CLI? I'm not a big C++'er but sounds like you are saying 2003/2005 should be used as it can completely replace the 6 version?
Yep.
C++/CLI is the VS 2005 version of Microsoft's managed C++ language. Prior to this version it was known as Managed Extensions for C++, which were a pile of poo. C++/CLI has a far more natural syntax for dealing with managed code, it a subset of C++ rather than Managed Extensions which had to conform with C++ compiler-specificity rules (such as double-underscore prefixes e.g. __gc for declaring managed classes).
VC++ 2005 completely replaces VC++ 6, yes. VC++ 6 is pretty bad in regards to compliance with the C++ standard, compared to 2003 and 2005.
Thanks PG. I will install VS 6 (no compatibility mode) but not the C++ app. I believe that this will still be stabil as the C++ part wont be installed.
This weekend is when I am planning to install my reqired programs on my new system and migrate over all my data files. :(
Yea, be the pioneer and don't forget to inform of every problem there will be... :D
Personally I'll wait until the first SP - won't take any chances after infamous Win3.1 to Win95 migration. :sick:
So far I have got VS 6 Ent. installed minus the C++ program and some of the VC++ Tools. No errors. Currently downloading the SP5+6.
Needed to run the setup.exe as administrator though and didnt use the compatibilty mode.
VS SP-6 now installed. Running just fine! :D
My first exe (no themes though as the manifest doesnt work under Vista).
http://vbforums.com/attachment.php?attachmentid=52797
http://vbforums.com/attachment.php?attachmentid=52798
anyone know yet how to enable the themes on the client area controls?
You are the only one running vista here .:)
Anyway check this site
http://www.vbthunder.com/ ,check out the "task dialog" sample.
He is an MVP himself,so maybe you would know him personally (http://www.mvps.org/links.html#VisualBasic).
Thanks. I'll take a look today.
I figured I would post this stuff anyways in case anyone is running a beta version or later the thread could be helpful to others when they start running it. :)
Hmm, seems the TaskDialog API doesnt exist in the comctl32.dll after all. I am trying to locate a new API viewer or such for the Vista APIs. MSDN has them in C++ format but still using the Dependancy Walker utiliyt it shows that the ones that are supossed to be in there aren't. :(
He was saying he tested it on a beta release.Maybe the redmondians decided to scrap it or would release it later as a service pack.
Thats very possible as I just confirmed with kleinma that his install of Vista RTM also gives the same "Cant find entry point" error for that example.
I sent the author an email so maybe he will have something else to add or update.
Couple of years back i read about an object oriented file system which was nicknamed "Winfs" and was supposed to be the de facto file system of Longhorn(then).Is there any thing like that in vista??or was it just another illusionary idea of M$.
It was meant to be in Vista but MS scrapped it as the development was taking too long.
Interesting.
I dont think its scrapped but rather delayed for a future release.
I'm still loading apps and doing a little researching. I wanted to start with the basics of implementing VS 6 on Vista and perhaps a few samples but its proving more time consuming then I tought it would be. Due in large part to it being so new and only a very limited amount of information on MS so far.
MS has talked about and promised an object oriented file system for almost 15 years now.
I found the TaskDialog API in the comctl32.lib of the Windows SDK but VB 6 wont let me add a reference to it. Maybe if I could tell the API to point to it?
maybe you should try what joacim did in his common dialog thread in the codebank section.
http://www.vbforums.com/showthread.php?t=77191
I'm thinking of overwritting the dll as Vista has Shadow Copies running by default. If it doesnt work then I can easily restore the previous version.
But then again, it shouldnt be this way. It should be in the default Vista version of comctl32.dll
Just for your information,Vista ui developers maintain an official blog at http://shellrevealed.com .Maybe they could suggest an alternative soln or something.
Yes, it looks like there is some good info there but everything is in C++ as its the dominant language used to write Windows.
I'll see what I can find but it does appear that there may be an update or something that will make it supported.
Seems that my Microsoft Optical Wheel Mosuse's wheel does not work in the VS IDE even with the correct updated Vista Mouse driver.
I got it to finall work. Turns out that the required comctl32dll version is in the side by side assemblies folder.
I can reference the folder in the API path but just trying to make it more dynamic.
Its located in - x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100
So you can see why I want to reference or link up to the dll dynamically.
Hey Yoda can u send me the manifest u are using on that program... or is it the vista theme?
It is one of Vista default "themes".
So if there are more than one copy of commctl dlls .How does vista decide as to which one to refer when an app calls an api?
kleinma has found that we can use the manifest trick to tell the exe which to use but it doesnt work in the IDE for debugging. I am looking into that currently.
Cont'd from post #28: One thing I did find was referencing the entire path in the API call works but I havent found if it can be relied upon as a static permenant path on all versions of Vista and isnt different file/folder name too.
Maybe there is a reason why that dll was sitting out there.Moreover that path doesn't really seem like a consistent one.
Its because VS 6 is really something that MS didnt want to support because its more of a legacy app now. Also, since it doesnt support integrating with Vista's Side By Side assemblies and SxS manifests is probably one of the main reasons.
Finally got time on this again and got it mostly complete. Figured out the Vista button themes issue as you can tell in the picture the buttons have the theme applied. Still working on dynamically linking the common controls but this will be posted soon.
:)
Try changing that shield to your avatar if it's possible . :lol:
Its not possible. I looked :D Only 4 choices are available. The Question mark icon is no longer available either. :(
Finally! It's been deprecated since Windows 2000. Apparently it was too easily confused with the Information symbol; and you're supposed to use Alert instead.Quote:
Originally Posted by RobDog888
edit: OK, 'Warning', not 'Alert'.
There is only 4 available icons now.
Just a quicky....
VB Code: