Search

Controls in CreateUserWizard WizardStep not visible as before by troy.zarger

Active

26
0
Sign in
to vote
Type: Bug
ID: 533071
Opened: 2/11/2010 6:35:07 PM
Access Restriction: Public
1
Workaround(s)
17
User(s) can reproduce this bug
I had code with VS 2010 Beta 2, where I had a wizardstep that had 2 textboxes and now they are not in the designer.cs file.
Details (expand)

Product Language

English

Version

Visual Studio 2010 Release Candidate

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

1. Drop a CreateUserWizard control on form
2. Add A Wizard step, and name it "Test" and move it up to be the middle step.
3. Change CreateUserWizard to Step: "Test"
3. Drop an asp:textbox on the Test container
4. Go to code behind, type "string test = TextBox1.Text;" and you will see it does not show up.

Actual Results

TextBox1 control is not persisted in designer.cs file

Expected Results

TextBox1 would be persisted in designer.cs file.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
File Name Submitted By Submitted On File Size  
CreateUserWizard.zip (restricted) 2/14/2010 -
Sign in to post a comment.
Posted by Microsoft on 3/5/2010 at 2:21 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 Eriawan Kusumawardhono RX on 2/27/2010 at 10:33 AM
Hi,

Microsoft, have you done your thinking on releasing this on RC fixes? I believe many of other VS 2010 RC users are asking for fix on this release BEFORE RTM, not ON RTM! How long do we have to wait for fixes? One month? Months until RTM comes out?
This is getting ridiculous! I'll wait for more 3 days. If I didn't get the fix, I'll be happy to downgrade to the good old VS 2008 SP1, and I'd like to spread this to customers at large, since you messed us all on this buggy RC release.
I'm beginning to lose my confidence on VS 2010! grrrrr
Posted by Microsoft on 2/25/2010 at 1:35 PM
We are actively working on a fix for this issue and looking into the possibility of releasing a patch for the RC release. If we are able to publish a patch for this issue, it will be publicized on http://blogs.msdn.com/webdevtools

In the meantime, we have published information about a workaround here:
http://blogs.msdn.com/webdevtools/archive/2010/02/18/workaround-missing-declarations-for-controls-in-designer-file.aspx
Posted by troy.zarger on 2/25/2010 at 8:50 AM
Yep, I agree... this workaround is not a viable solution... I am a bit disappointed with the lack of fast action by Microsoft on this ... especially when it worked in Beta 2... and this has a Go Live License... so much for going live. If we could get a hotfix for this, then I could continue testing... the thing that scares me, is if they wait until RTM, there may be other glaring bugs that do not get fixed since anyone with a WAP cannot really move forward.
Posted by Rubens Cury on 2/25/2010 at 6:08 AM
Agracemo your commitment and suggestion in an attempt to "circumvent" this bug, but I think it is impossible to use them in the development of any application.

Using your suggestion for a resolution that would change all the page frames after this bug was fixed.

I suggest we all keep voting for this bug to try to expedite this solution.
Posted by Tatworth on 2/23/2010 at 8:13 AM
I have done a demo of the problem and its manual fix at http://vs2010rc1fix.codeplex.com/
Posted by Tatworth on 2/23/2010 at 2:35 AM
I am using VS2010 RC1 and I have just created a Wizard Control. Labels within the Wizard control are not accesible. I have just checked the MSDN documentation at http://msdn.microsoft.com/en-us/library/wdb4eb30.aspx which shows that controls within the control steps should be just as accessible as controls within the rest of the form.
Posted by Tatworth on 2/23/2010 at 12:39 AM
Re I have added a solution which fails to build for me which shows the example. by troy.zarger on 14/02/2010 at 09:51

I cannot see the solution you added. Please post post it at http://forums.asp.net/p/1527563/3693973.aspx
Posted by troy.zarger on 2/22/2010 at 5:03 PM
Yes, see the third message...

Posted by troy.zarger on 2/14/2010 at 9:51 AM
I have added a solution which fails to build for me which shows the example.
Posted by Tatworth on 2/22/2010 at 9:09 AM
Have you published a demo project for reproducing the problem?
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:10 PM
Also the same issue as bug 533302.
Posted by Martin.Robins on 2/19/2010 at 12:02 PM
This is the same issue as is reported in bug 532641 - all of you who have upvoted this issue and/or confirmed that you can reproduce the problem please also add your weight to the related item so that it becomes clearer that we need it fixing.
Posted by Rubens Cury on 2/19/2010 at 6:47 AM
Final Release? As long as I know not yet even an estimated date of this release.

Excuse me, but I think that this problem occurred in a very specific scenario there would await the final release, but the RC with it becomes absolutely useless.

What you will do with Visual Studio 2010? This is the phrase of disclosure that Microsoft has used. The users' answer we already know...

I can't believe that this bug exists in an IDE that level. I would like to appeal to other users so that they manifest themselves as much as they can.

Microsoft, I suggest disabling the download of the RC, because it does not work.
Posted by Aaron Smith on 2/19/2010 at 6:44 AM
This is a very serious issue and completely stops me from using the RC at all. Anytime I open a page and modify it, all my controls are removed from the designer file. I then have to open the project in 2008 and delete the designer file and have it recreate it. I might as well just use 2008 instead of 2010. You need to release a hot fix for this or all web testing is for naught.
Posted by troy.zarger on 2/18/2010 at 2:58 PM
Unless Final Release is going to be next week... What good is a Go Live License? Especially since this is a blocking issue... Not like a random crash for a very specific scenario... which you released a hot fix for...
Posted by Microsoft on 2/18/2010 at 11:22 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 10:37 AM
This is very serious issue and completely blocks web site development in one of our projects
Posted by Rubens Cury on 2/17/2010 at 3:54 PM
Hi,

I'm getting exactly the same problem.
Unfortunately it is impossible to start the development of any application with this bug.

Using the Beta 2 I was not having problems. I think this is a serious bug.
Posted by troy.zarger on 2/16/2010 at 4:19 PM
Any update? Any possibility of an interim build that has this fixed?
Posted by troy.zarger on 2/15/2010 at 3:41 PM
Great, glad to hear it. So I have been developing several new applications which are still in development, but now with this I have almost every application broken due to this issue. It applies to callback panels, etc... not just the CreateUserWizard.

So with that in mind, will there be a hotfix for this immediately, or will be forced to wait for next RC or RTM? With a GoLive License, wouldn't that include hotfixes?

If I have to wait, I will be forced to drop back to Beta 2 of VS 2010, a real shame. Please advise immediately, thank you.
Posted by Microsoft on 2/15/2010 at 3:44 AM
Thanks for your feedback again!
We were able to reproduce the issue with this project you uploaded. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by troy.zarger on 2/14/2010 at 9:51 AM
I have added a solution which fails to build for me which shows the example.
Posted by Microsoft on 2/13/2010 at 10:43 PM
Thank you for taking the time to report this issue.But we are unable to reproduce this bug.Could you please attach a zipped project to help us reproduce it?
Posted by Microsoft on 2/12/2010 at 7:02 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.
Posted by Tatworth on 2/23/2010 at 8:14 AM
It can be manually fixed - please see the demo of the problem and its manual fix at http://vs2010rc1fix.codeplex.com/