Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Extensibility / April 2008

Tip: Looking for answers? Try searching our database.

Vs2005, 2008 and Vista

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jan - 10 Apr 2008 14:35 GMT
we have a project package that reads from the HKLM\Software registry tree,
the same code runs in vs2005 and vs2008 for this. On Vista, when I run VS as
normal user (not admin) and view with procmon, I see that opening the key
works in VS2005 but fails with 'access denied' in VS2008. Is there a
difference in the way both VS's handle packages?
Wen Yuan Wang [MSFT] - 11 Apr 2008 12:32 GMT
Hello Jan,

It sounds the project package works fine with VS 2005&Vista, but failed on
opening "HKLM\Software" registry tree with VS 2008&Vista. If I
misunderstood anything here, please don't hesitate to correct me.

Most VSPackages that work in Visual Studio 2005 will continue to work in
Visual Studio 2008 without modification. Most services, entry points, and
events maintain compatibility, but there are some exceptions, which are
listed later in the following topic.
http://msdn2.microsoft.com/en-us/library/bb166245.aspx
[Migrating VSPackages to Visual Studio 2008]

For your case, could you let me know which specific registry key did VS
2008 try to open?
Is it ""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8"?
I will appreciate if you can send me your procmon trace log. This could
help on research very much. My email address is v-wywang@microsoft.com

Have a great day,
Best regards,
Wen Yuan
Microsoft Online Partner Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
jan - 14 Apr 2008 16:16 GMT
hadllo Wen,

thanks for your offer, but I found what is wrong: the wizards definition
file (x.vsz) holds a version number that should be 9.0 for VS2008. We still
had 8.0 there, so it worked as long as VS2005 was also installed on the
system. Nothing to do with Vista or Server 2008!

Regards,
Jan

> Hello Jan,
>
[quoted text clipped - 21 lines]
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
Wen Yuan Wang [MSFT] - 15 Apr 2008 09:10 GMT
Hello Jan,
Thanks for your reply.

I'm glad to hear this great news.
It seems the wrong version number which defined in x.vsz file results the
issue. You figured out the root cause, and resolved the issue.
If you face any further issue, please feel free to let us know again. :) We
are glad to assist you.

Have a great day,
Best regards,
Wen Yuan

Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.