issue with auto-generated Designer files not addding components

File Name	Submitted By	Submitted On	File Size
msoft 2010 rc designer issues.txt (restricted)	jayc2	2/12/2010	-
test98.zip (restricted)	jayc2	2/16/2010	-

Posted by paul.gibler on 2/24/2011 at 9:26 AM

This "feature" has proven to be a nuisance oftentimes when I'm working with many web controls and making quick modifications to all of them. I should be able to leave my .ascx files in CodeFile mode, add subcontrols to them, and be able to access those subcontrols in the related .cs file and have access to those fields immediately. I see no reason why this should not be the default behavior.

If this feature works on x86 systems but not x64 systems, it should be considered a bug and not a feature on the x64 systems. Please fix it as I would rather use 2010 than 2008.

Posted by millz1 on 2/24/2011 at 9:25 AM

Fwiw, I'm in the same boat. My company develops on Windows 7 x64, and we cannot upgrade our projects to VS 2010 until it is resolved.

Posted by Jeetendrav on 2/3/2011 at 8:33 AM

Hello, I have the same problem with VS2010 Profesional - designer.cs file is generated incorectly. I've tried to install pacth KB981167 but this error occured: KB981167 does not apply, or is blocked by another condition on your computer. Please let me know how to fix it. My Machine is running on Windows XP professional

Posted by jgrewe on 1/3/2011 at 7:25 AM

Can this please be fixed in x64 systems as we will have to go back to Visual Studio 2008 if not.

Thanks!

Posted by chris sulham on 12/7/2010 at 12:49 PM

Any word on a fix for x64 systems? I'm still seeing this issue in Win7 x64.

Changing a user control to CodeBehind forces the designer to regenerate, but breaks intellisense in the code file. Setting a user control back to CodeFile restored intellisense but any controls added/edited in the markup file do not appear in the designer.

This is an annoying issue and we'd appreciate a fix.

Posted by Vs2010Dummy on 10/19/2010 at 6:12 AM

Still doesn't work. KB981167 will not apply to Win7/X64 systems. this is holding up developement houses, it has been fixed on X86 systems. Is X64 that different ?. The workaround does not work on Win7/X64 sysems where projects were originally configured as WEB APPS ! (convert to web app has no effect).

Posted by frogydev on 8/12/2010 at 11:40 PM

Hello, I have the same problem with VS2010 Profesional - designer.cs file is generated incorectly. I've tried to install pacth KB981167 but this error occured: KB981167 does not apply, or is blocked by another condition on your computer.

Posted by HangLi on 7/24/2010 at 10:31 AM

I have the same problem with Visual Studio Express 2010. it says "KB981167 does not apply, or is blocked by another condition on your computer" when installing VS10-KB981167-x86.exe .
converting to web application did not solve the issue.

any more suggestions???

Posted by nanopp on 4/23/2010 at 8:30 AM

Posted the Solution that worked for me, used the new "Convert To Web Application" option.

Posted by nanopp on 4/23/2010 at 7:06 AM

We just migrated all our project to VS2010 Release 10.0.30319.1; Our Web project that has 2 years in intranet production has now around 10.000 compilation errors!! and this appears to be because this bug persists in the realease. Our main issue seems to be that code-behind files are not recognizing any control in Markup. Something as simple as <asp:Label ID="lblTitle" runat="server" ></asp:Label> FAILS if I have to access this control via code-behind.

The Patch VS10-KB981167-x86.exe is not working for me, since its telling me its not applicable to my VS.

Please HELP, this is a MAJOR Issue, it is completely blocking our Web Development in production, since we innocently migrated trusting in Microsofts final release. our web application is Published using VS2008, and now if this is not fixed soon, we will need to downgrade to VS2008. PAINFULL process.

Posted by Vs2010Dummy on 3/25/2010 at 4:32 PM

On march 24th windows update installed updates which RE BROKE THESE!, (must have covered up code
for HotFixes, ANYBODY ELSE NOTICE THIS?, The VS10-KB980920, and VS10-KB981167
worked from march 8th until march 25th !!

Posted by Vs2010Dummy on 3/9/2010 at 10:23 AM

Thanks Guys, it seems to be fixed and working correctly!

Posted by jayc2 on 3/9/2010 at 5:16 AM

based on my testing with a pretty big webpage and changing things around. It appears that that designer file is now being populated correctly. Nice work. Now back to work.

Posted by Microsoft on 3/5/2010 at 2:22 PM

A patch for this issue for Visual Studio 2010 RC is now available for download:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=27117

Posted by Vs2010Dummy on 3/2/2010 at 10:58 AM

Microsoft Please FIX THIS, it is shutting down Software developement Houses. Everytime we touch a aspx. we have to
stop and manually add temp code. For those of us who are developing hundreds of ASP NET applications, this is a SERIOUS show stopper. It takes to long to roll back to beta 2. All this worked in Beta 2, HELP US.

Posted by Eriawan Kusumawardhono RX on 2/26/2010 at 4:47 AM

I have been early adopter too. Now I'm switching back to Beta 2 because of this nasty bug! It's clearly reproducible, and it's also a fatal bug, why do I have to wait for RTM? PLEASE FIX THIS SOON IN RC Build!

If you, Microsoft, said that we have to wait for final RTM to fix this, why do this bug gone unnoticed at Microsoft by the time RC released? At some point you asked for feedback, then you forced us to wait for RTM, as told in MS webdevtools blog.
Again, please fix this before RTM and patch this bug in the RC release!

Posted by RyanHoff on 2/21/2010 at 8:40 AM

Microsoft -

This is a huge blocking ASP.NET development issue. Do you guys want people to use .NET 4.0 for their ASP.NET projects? Do you guys want the RC tested in ASP.NET scenarios? FIX THIS ISSUE. RELEASE A HOTFIX FOR THE RC. As a company who have been early adopters of .NET 4 since Beta 1, we are at a point where our entire ASP.NET application has become completely broken because of this issue. We're talking nearly a year of development. We now have a hard dependency on .NET 4 - we can't simply go back to VS2008. Please Microsoft, release a hotfix for this issue.

Posted by DigitForge on 2/19/2010 at 12:20 PM

And bug 534086

Posted by Martin.Robins on 2/19/2010 at 12:16 PM

This issue is also reported in bug 533945.

Posted by Martin.Robins on 2/19/2010 at 12:08 PM

This is the same problem as reported in bugs 532641 and 533071. The more I look through the list of issues raised (which is not easy by the way as the list always starts back at the beginning if you navigate using the back button) the more times I am seeing this issue and it is as important to everybody that this is resolved as a matter of urgency if you want people to be able to test the RC and provide any additional feedback.

Posted by DigitForge on 2/19/2010 at 11:35 AM

I agree with needing a hotfix. I would like to continue testing the RC and providing feedback, but this puts us dead in the water for using CV2010 on about 90% of our projects (that are web based). I also understand this is still unreleased and we should expect bugs, so please do not take this as we expect a fully working version. But it does prevent us from moving forward with testing VS2010 atm.

Posted by Aaron Smith on 2/19/2010 at 6:46 AM

I think you need to do more than just consider releasing a patch. This stops many people from using the RC at all, including me. I'm going to have to revert all development back to 2008 at this point. A hot fix is is needed ASAP.

Posted by Microsoft on 2/18/2010 at 11:28 AM

Thanks for the report. Many customers are running into the same issue with other controls. We are working on a fix for this problem for the final release. We are also considering releasing a patch for the RC build.

Posted by Microsoft on 2/18/2010 at 11:25 AM

Thanks for the report. Many customers are running into the same issue with other controls. We are working on a fix for this problem for the final relase.

Posted by Andrew111 on 2/18/2010 at 11:21 AM

There should be hotfix for this. This bug completely blocks our website development.

Posted by jayc2 on 2/18/2010 at 4:42 AM

plz a private hotfix or a fast turnaround is needed. I am trying to push the limits and use bleeding edge stuff in .net 4.0 related to the entity framework and other updates. I am stuck. I went back to VS 2008 and I am stuck until this gets addressed. using findcontrol is beyond a pain, so is manually adding the reference.

Posted by troy.zarger on 2/16/2010 at 1:08 PM

Can we not get an interim build even if you are not going to publish a hotfix?

Posted by jayc2 on 2/16/2010 at 12:04 PM

oh, and how long are we going to wait for what I think is a pretty big bug? 1 month, 6 months, 1 year?

Posted by jayc2 on 2/16/2010 at 11:52 AM

how would you manually declair a control without causing issues down the road? can you please provide an example relative to my project uploaded or point me to a location that has an example. Thanks

Posted by Microsoft on 2/16/2010 at 11:29 AM

Sorry to hear you've had to move back to VS2008, though I can definitely understand how this issue affects your productivity. Unfortunately the only workaround at the moment is to declare your controls manually in your .cs/.vb file. We are currently working on a fix which will address this for the final release.

Posted by jayc2 on 2/16/2010 at 9:10 AM

At this time, I have had to revert back to using vs 2008 as my dev environment. I develop strictly for web, so until this issue is resolved it is hard to continue testing/using VS 2010. I have not found any other outstanding issues at this time. The performance is getting better. Not quite up to vs 2008 but close. Is there a way to workaround this current bug until a patch is available?

I am looking forward to testing the use of the integrated debugging as I had a bunch of anoying issues with debugging in beta2 where the debugger would start and hang.

I love the new interface, the ability to use my full extended desktop ROCKS.

I am quite confused as to how this New Help system even works. I would like to be able to add help databases to local help. For example, I use components from developer express and others that have help files that I can not directly access via the VS environment.

Looking forward to the patch.

Posted by Microsoft on 2/16/2010 at 8:50 AM

Thanks for attachment and the feedback. Is this the only "basic functionality" you feel is missing from the product? Or are you seeing some other basic testing gaps in the RC?

Thanks,
John Dundon
Visual Web Developer Team

Posted by jayc2 on 2/16/2010 at 6:08 AM

I am so looking forward to VS 2010 living up to it's potential. I am very happy with the progress MSOFT! I am somewhat disappointed in the lack of basic functionality testing that went into going from beta2 to RC. I understand that this is a big project. BUT this is like creating a spellchecker and releasing it without checking if it spells things right.

Posted by jayc2 on 2/16/2010 at 5:04 AM

attachment is included. Thanks

Posted by Microsoft on 2/15/2010 at 4:41 PM

Yes, we have identified some issues with the RC that have to do with generation of designer files. However we would like to make certain that your problem is addressed by our fixes - would you possibly be able to upload the web site (or simply the aspx page if that's easier) that isn't getting generated properly in VS2010?

Thanks,
John Dundon
Visual Web Developer Team

Posted by troy.zarger on 2/13/2010 at 7:11 PM

I would like to say there seems to be several issues with the rc designer files... I have the problem with the CreateUserWizard, as well as some DevExpress components.

Here is my issue that may be the same as this...

https://connect.microsoft.com/VisualStudio/feedback/details/533071/controls-in-createuserwizard-wizardstep-not-visible-as-before

Posted by Microsoft on 2/12/2010 at 7:08 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)

issue with auto-generated Designer files not addding components by jayc2