I hope that other out there have had the same issue that I am having.
I am running VS 2005 Beta 2.0 and trying to compile a simple ASP.NET
Web app (C#) and I keep getting this error in the WEB.CONFIG:


The specified module could not be found. (Exception from HRESULT:
0x8007007E) This is on MY Line 42, which is this tag:

<compilation>


Any help on this would be appreciated. It's frustrating as all sin!

Let me know if you find a solution to this. I am getting the exact
same message. I wasn't getting this problem yesterday, with a
different project, but today, it started happening. I think it is a
2005 thing, but haven't figured it out yet. I will let you know if I
find anything out.

Mark

Thanks..I will surely post any responses I get.

Thanks Mark. This is something none of us here thought of. We use a few
third party components here as well. I'll let you know our results.
Thanks for the information :)

I just thought I would let you know I am getting further in my investigation
of this problem.

Basically, a little background on my website. I have a website set up that
is also being used for remoting objects. In ASP.NET 1.1, we had a BIN
folder that contained all of my assemblies. From what I have read, there
are now multiple options for 'compiling' the website. Anyway, I moved some
files under the App_Code directory, and those get compiled fine. However,
when I added some references to some of my other Assemblies, that is when
things started blowing up.

When I add the references, it put a bunch of files in the BIN directory
(where it used to be in 1.1 as well). If I try the 'Default.aspx' page
after that (just a basic page that displays 'Hello World'), it errors with
the error you and I are getting. If I remove the files from BIN, it works
fine.

Anyway, what I tried doing was removing all of the files from BIN and adding
them back, one-by-one. I got to a third-party assembly I used (but not sure
I need) and when I added it, it failed, but when I pulled it out, it worked.

Anyway, I am still researching it, to determine if that is what is causing
ALL of my problems or not. I'll post another response, once I determine if
that is my ONLY problem.

You might want to try it out and see if you have the same results.

Mark


[quoted text, click to view]

Mark,

You know what, I think you hit it correctly on the button. As soon as I
started removing referenced components 1 by 1, I found the DLL that was
causing the problem.

When I got to our LEAD Tools .NET refernce in the project, I removed
the LeadKernal.dll and that is the one that was causing a problem.
Considering though that our assemblies are the only ones using this, it
was kind of odd that it was sitting in the WEB Project reference in the
first place. Anyway, I think I can say that you lead us in the right
direction.

Thanks a ton for the help!

Glad your problem was similiar to mine (well, I guess I am glad!). Anyway,
I don't understand it either, but that does appear to have fixed my problem.
In my case, I didn't need the assembly in the web project, but it was being
brought over when I added the reference. I don't understand it.

Anyway, I hope that is the last of that one. That error was NOTHING like
what the problem eventually ended up being.

Good luck, and let me know if you find any additional info on this.

Mark

[quoted text, click to view]

When the RTM version of VS 2005 was released I did a reinstall of my
system, OS and everything, to ensure that I did not have any old bits
lurking about. After installation and fetching the source to my projects
from source control the website would not build no matter what. I got
the Exception from HRESULT: 0x8007007E exception straight away. I tried
to add any missing assemblies but nothing worked.

By coincidence I noticed that the reference list on the website
properties page was only displaying a couple of the System.* dll's as
well as a version of the Office assembly. Once I removed the Office
assembly all the assemblies in my \Bin folder appeared as they should.
After this everything is working good.

My system is running Windows 2003 Server, Office 2003 Pro and VS 2005
Pro.

Kim