Hello Axel,
According to your description, you got an error message reads "there is no
build provider registered for the extension" when opening aspx pages in
source view. If I misunderstood anything here, please don't hesitate to
correct me.
This line of error message means VS IDE cannot found build provider
registered for .aspx extension.
Does this issue occur on each web project on your machine?
1) If it only occurs on your current project, please check your project
web.config file.
Did you add the entry as below in your config file? If so, please remove it.
<buildProviders>
<clear/>
</buildProviders>
2) Otherwise, please check your web.config in the .net framewok folder
(C:\Windows\Microsoft.NET\Framework\[version]\CONFIG) if the issue occurs
on each web project on your side.
Is the following entry located in your config file? if not, please add it.
<buildProviders>
<add extension=".aspx" type="System.Web.Compilation.PageBuildProvider"/>
3) At last, if the issue still persists, please register build provider in
your project web.config file directly.
<buildProviders>
<add extension=".aspx" type="System.Web.Compilation.PageBuildProvider"/>
Hope this helps. Please try the above method and let me know if this works.
We are glad to assist you.
Have a great day,
Best regards,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Axel Dahmen - 17 Jan 2008 19:26 GMT
Thanks, WenYuan, for trying to help.
I did a repair on the VStudio installation already, which fixed the problem.
Apparently something was missing in the registry when I switched to the new
user (which is the same user name as the old one but under a new domain).
As to your question: Unfortunately, at my customer's I have only got this
single project on my machine but I assume it's a machine configuration
problem. I haven't changed anything in the <buildProviders> section of any
.config file on my machine. Just was assigned to a new domain.
Perhaps your (and mine) information can act as a help for someone else who
also encounters the same problem. I've seen this question being asked a
couple of times but no helpful answers had been given.
Your help was quite appreciated.
Best regards,
Axel Dahmen
----------------------------
> Hello Axel,
>
[quoted text clipped - 37 lines]
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
WenYuan Wang [MSFT] - 18 Jan 2008 07:04 GMT
Hello Axel,
It seems repairing VS could resolve the issue. I think this maybe accuse by
some wrong configuration file.
Thanks for your reply and sharing the information with us. Others may learn
and benefit from your information. :)
Have a great day,
Best regards,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.