Hi

Am i doing something wrong? because i don't get compiler errors in my aspx pages. and when i refactor my code, the changes don't affect the aspx pages.

I remember reading somewhere that this should be happening. (probably a post on this forum) 

Hi ,

Well don't think refactoring has any thing to do with the compilation errors you are getting and don't think what refactoring would solve the problems. Try looking at the error list to find out what exactly is wrong with your application

 I've been having the same issue. Life's just not going to be the same until R# 4.0 is released.

I have the same problem and I just assumed it's R#, so I just deal with it. I can't live w/o R# 

Yes, I am not using R# until 4.0 is released as it screws up lots of the lambda/ linq code. So, on that note, its not R#'s problem necessarily.

Had a look around but it's not that easy to search for R# (the # just gets ignored).

What is it? Where can i find out about it?

Are you sure that this isn't supposed to work by default? i'm going to try to find the article i read which mentioned this. i'll post it here later when i find it. 

I was saying I think it should work by default. Another commenter said he thought it was R# (Resharper) that was causing the issue as Resharper doesn't fully support 2008. I'm not using Resharper as it doesn't support LINQ, Lambda, and who knows what else... probably automatic properties as well, so it would throw errors on legitimate code.

If you haven't used Resharper, I would highly recommend downloading a trial for 2005 and checking it out. It makes life so much easier.
 

 Resharper from Jetbrains. You have to check it out.

Ahh yes, Resharper, know it, love it, going to convince the boss to buy it for us.

Never referred to it as R# tho, surely it should be Re#er, lol. Plus there's a sourcefource project called R#, very confusing.

Anyway, yeah this isn't about Resharper. I couldn't find the article i was talking about. It was about the MVCToolkit, saying that using the lamda expressions like...

<%= Html.ActionLink<HomeController>( x => x.Index(), "Home" ) %> 

...would respond to visual studio refactorings like Rename if i renamed the controller or the method name.

I guess they were either mistaken or using unreleased bits.

So, should this be possible in VS2008 without any 3rd party apps?
 

I remembered where i heard this should work.

It was Scott Hanselman's video from http://www.asp.net/downloads/3.5-extensions/

no wonder i couldn't find the article. lol. 

It does not work for me. In VS2008, I renamed a controller class and the built-in refactoring did not change any of my html.actionlink<controllername>(...) in my aspx files.

Can somebody from the asp.net team please confirm whether the refactoring that you tout will work out-of-the-box in visual studio? or do we need to get third party tools to do it?

Having the same problem. While I can see not being able auto rename on refactor being annoying, I think its even WORSE that we're not getting compiler errors.

 That is, as tgmdbm pointed out, if I have somthing like:

<%= Html.ActionLink<xController>(x => x.index(), "Home") %>

and I rename the xController class to yController the compiler DOESN'T yell at me about the error in the view on build. I just get runtime errors. To me this kinda defeats to purpose of using the lambda for strong typing in the first place.

Any advice as to the cause/work around or explination of the expectations being incorrect would be greatly appreciated.

 Thanks everyone!

For some strange reason, visual studio doesn't do this.  

Resharper is the future.