Search

ASP.NET Wizard Control introduce breaking changes by wagneripjr

Closed
as Fixed Help for as Fixed

3
0
Sign in
to vote
Type: Bug
ID: 534564
Opened: 2/18/2010 7:25:39 AM
Access Restriction: Public
Primary Feedback Item: 532641
0
Workaround(s)
2
User(s) can reproduce this bug
I was working with a solution created in VS2008 targeting .NET 3.5.

The migration to VS2010 was OK, It compiles and runs OK. Then I did a lot of development without any problems.

Today I've changed one word on the aspx of a page I did not change before and broke my build. VS2010 complains that a lot of controls doesn't exists with the message: "The name '...' does not exist in the current context".

I did code this page referencing components directly because in VS2008 the Wizard is like MultiView, now It is like data-bound controls and one must use FindControl to access anything inside it.

I see two problems here:
1 - The control should not introduce breaking changes when targeting an old framework;
2 - The migration wizard did not warned about it;

I compared the source code with the previous working version and all control declarations were removed from designer.cs

The problem could be only with the form designer that not did not use a diferent behavior for the targeted framework version.
Details (expand)

Product Language

English

Version

Visual Studio 2010 Release Candidate

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

Create an web application targeting framework 3.5
Add a wizard control
Add a textbox to step1 inside the Wizard
Save
Try to code:
TextBox1.Text = "It's OK";

It does not compile; Do the same in VS2008 and it compiles.

Actual Results

Does not compile

Expected Results

Compilation ok
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/22/2010 at 4:17 PM
Resolving this as a duplicate of the issue reported at:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=532641
Posted by Microsoft on 2/18/2010 at 7:05 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.