Home Dashboard Directory Help
Search

Visual Studio responses with Classfactory cannot supply requested class by Alexander Demidovich


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 532500
Opened: 2/10/2010 2:46:35 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Disabling of Visual Theme in Compatibility Settings (shortcut for devenv.exe) turns to inability to open or "save as" any files and projects in Visual Studio Environment. Visual Studio responses with "classfactory cannot supply requested class" and that's all. Removing of this setting restores the normal behaviour - I can open and save the files

I tried to disable this setting for other applications and didn't see any problems. Everything works perfectly.
Details
Sign in to post a comment.
Posted by Microsoft on 7/12/2010 at 4:32 PM
Thanks for your feedback. We have confirmed that this is indeed an issue and we'll bring it up during SP1 planning. If you feel strongly about this bug please encourage others to vote it up so we can prioritize issues accordingly.

Thanks,
Matt Kaufman
Program Manager - Visual Studio Platform
http://blogs.msdn.com/b/visualstudio

Posted by Microsoft on 7/12/2010 at 4:31 PM
I've fixed this issue in our latest internal build. It's not yet certain whether or not the fix will be available in the service pack or in VS 11.0, but you should see the fix in a future release.

Thanks,
Matthew Johnson
Developer - Visual Studio Platform
Posted by KevinS734 on 7/8/2010 at 1:07 PM
In case this information is useful for future consideration: You asked why someone would run VS2008 under compatibility settings. In my case, I selected "Disable visual themes" to prevent significant flicker in the Solution Explorer when navigating through an ASP/ASP.NET file. I am using Win7 x64.
Posted by Microsoft on 3/12/2010 at 5:45 PM
Hi UltimateQuestion,

Thanks for your feedback, unfortunately at this point the Visual Studio 2010 release is locked down, and this bug does not meet the bar for a 2008 servicing patch. We will review this issue again for sp1, in the mean time we apologies for any inconvenience caused, and thank you for bringing this issue to our attention.

The Shell Team
Posted by Alexander Demidovich on 3/8/2010 at 11:36 PM
Hello

yes, the same problem appears in Visual Studio 2010 RC1. When I disable "Visual themes", a "Open File" dialog doesn't work anymore. I'm getting the same error "classfactory cannot supply requested class"

Should I report the bug for 2010 or it's enought here?
Posted by Microsoft on 3/5/2010 at 7:17 PM
Hi UltimateQuestion,

Thanks for your feedback in this area, have you tried your scenario in the RC release of Visual Studio 2010? Does the same issue occur?

Thanks for your time,
The Shell Team
Posted by Alexander Demidovich on 2/23/2010 at 7:51 PM
Because VS 2008 is slow. Disabling of Themes makes it a bit faster, especially in Windows 7.

P.s.: I know, there is VS2010 on the road, but not everybody updates immediately
Posted by Microsoft on 2/19/2010 at 12:07 PM
Hi UltimateQuestion,

We are closing this bug since we have not had a reply from you in over 7 days. You can re-activate this bug at any time.

Thanks for your time,
The Shell Team
Posted by Microsoft on 2/11/2010 at 9:14 PM
Hi UltimateQuestion,

Thanks for your feedback, could you please clarify your requirement for running Visual Studio under app compatibility settings?

Thanks for your time,
The Shell Team
Posted by Microsoft on 2/11/2010 at 12:14 AM
Thank you for reporting the issue.
We were able to reproduce the issue with the detail steps you provided. We are escalating this bug to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release.
Posted by Microsoft on 2/10/2010 at 7:01 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.