Last post Nov 05, 2008 08:21 PM by firstname.lastname@example.org
Sep 04, 2008 05:45 PM|NotChad|LINK
I'm working with a solution with many projects, there is some cross sharing.
I'm in VS2005/2.0 on Vista/iis7.
My original issue came about when I tried to add a new asp:DropDownList control to a user control, to add some new functionality
I saved the .ascx file, then went to the codebehind to work with the newly added control.
The code behind couldn't recognize the newly placed drop down.
I came to discover that the designer.cs file was not updating like it should.
I deleted the designer.cs file, then recreated it by right clicking on the .ascx file and choosing 'convert to web application', which I've heard forces regeneration of the designer.cs file.
It failed to renerate, saying it can't recognize a custom tag prefix. makes sense at this point why the designer.cs file wasn't updating when the new dropdown was placed.
So I made sure all everything was in place for the tag prefix to work, it's all there and works fine on OTHER projects (web applications projects) within the solution.
Then I noticed the error being thrown on the very top line of the file, for example:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="WebForm1.aspx.cs" Inherits="blahblahNamespace.WebForm1" %>
The error is "blah blah ASP.NET runtime error: Could not find a part of the path blah blah" pointing to a path that doesn't have or shouldn't have anything to do with this project.
This error is on EVERY page/control/etc in the project.
When I add a new form, it's on the brand new form also, thus seems to be a project specific issue.
When I do a build, I get a new error on the prior existing page I was working on in the first place:
"blah blah ASP.NET runtime error: There is no build provider registered for the extension ''. You can register one in the <compilation><buildProviders> section in machine.config or web.config. Make sure is has a BuildProviderAppliesToAttribute attribute
which includes the value 'Web' or 'All'. "
I'm guessing this is related to the non working custom tag prefix which is specified in the web.config.
I can work around my primary/first issue by manually updating the designer.cs file to get my new DropDown to work, but I need to figure out what's going on with this project
In my eyes the core issue is the error on the top line of all pages/forms/controls (both existing and new added) which I'll repeat here to summarize:
It's somehow/where looking for a path that's shouldn't be related to this project
Sep 04, 2008 08:57 PM|mydreams|LINK
Sep 12, 2008 03:02 AM|NotChad|LINK
it's not something simple.
i add a new form to this project and do nothing else and i still get the error above...
(sorry for the untimely replies, I found that I had my email wrong, so wasn't getting emails that replies were posted)
Oct 28, 2008 06:13 PM|tranlongphu|LINK
Hey guys, here's how to fix:
Or you can copy someone else web.config and machine.config and override yours in your framework folder
Nov 05, 2008 08:21 PMemail@example.com|LINK
Please paste your code