Thanks for your quick response Robert,
Glad that you've found the solution. Aslo, yes as you mentioned, in 2.0
since there is no longer explicit project files for asp.net application,
the project structure all depend on a well-defined folder structure, I'd
suggest you separate those parent/sub applicaiton if they're not nested or
coupled from business or application code logic perspective. Also, for
separate applications, it'll be better to upgrade them separately also.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| Thread-Topic: Reference Issue converting site from 1.1 to 2.0
| thread-index: AcXeg4AarkE84etVRqeWrFDvfWtIdQ==
| X-WBNR-Posting-Host: 67.180.214.235
| From: =?Utf-8?B?Um9iZXJ0?= <
[email protected]>
| References: <
[email protected]>
<
[email protected]>
<
[email protected]>
| Subject: RE: Reference Issue converting site from 1.1 to 2.0
| Date: Mon, 31 Oct 2005 17:28:02 -0800
| Lines: 132
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.aspnet:135135
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Okay, I found a solution...sort of odd to me though.
|
| Apparently under 2.0, if there is a problem with binding with the root
| application, it affects the sub applications....i.e. the error was really
at
| the root but mainfested itself when i went to the subapplication. Once i
| corrected the binding issue in the root application, then everything was
fine.
|
| Thx.
| R-
|
| "Robert" wrote:
|
| > Hi Steven,
| >
| > yes your correct in your restatement of the issue and I agree that the
| > subapplication should not be referencing the assembly. I checked the
| > web.config for the subapplication and dit does not reference the
assembly.
| >
| > I did not check (yet) the root application's web.config but it would
| > reference the assembly of course.
| >
| > I will re-compile and reproduce the error and look at the detailed
output of
| > the error and see if that gives more info.
| >
| > Thx and i will report back if i am unable to resolve this today.
| >
| > "Steven Cheng[MSFT]" wrote:
| >
| > > Hi Robert,
| > >
| > > Please ignore my first message since it's a wrong post, sorry for the
| > > inconvenience.
| > >
| > > Regarding on the problem you mentioned in this thread, when you try
| > > converting a whole asp.net 1.x web site to ASP.NET 2.0 project,
you're
| > > getting file/assembly not found problem in some sub web application
under
| > > the site ( and the reported asembly is not used by the sub project
but
| > > used by the root site app) ,yes?
| > >
| > > If there're anything I misunderstood, please feel free to let me know.
| > > Based on my experience, those static assemblies reference info are
embeded
| > > in assembly's manifest and this won't be inherited by sub site. On
think
| > > which could be inherted by sub directory/web applciations in asp.net
are
| > > the web.config settings. So I think you can try check the root
application
| > > and sub application's application web.config file to see whether
there is
| > > any settings which has referenced that particular assembly. In
addition, is
| > > the error message indicate where did the convert tool going to locate
the
| > > missing assembly, did it output the path?
| > >
| > > Thanks,
| > >
| > > Steven Cheng
| > > Microsoft Online Support
| > >
| > > Get Secure!
www.microsoft.com/security
| > > (This posting is provided "AS IS", with no warranties, and confers no
| > > rights.)
| > >
| > >
| > >
| > > --------------------
| > > | Thread-Topic: Reference Issue converting site from 1.1 to 2.0
| > > | thread-index: AcXdz5HqIpwhIDQWRGivf3qOhPqM3Q==
| > > | X-WBNR-Posting-Host: 67.180.214.235
| > > | From: =?Utf-8?B?Um9iZXJ0?= <
[email protected]>
| > > | Subject: Reference Issue converting site from 1.1 to 2.0
| > > | Date: Sun, 30 Oct 2005 20:00:02 -0800
| > > | Lines: 33
| > > | Message-ID: <
[email protected]>
| > > | MIME-Version: 1.0
| > > | Content-Type: text/plain;
| > > | charset="Utf-8"
| > > | Content-Transfer-Encoding: 7bit
| > > | X-Newsreader: Microsoft CDO for Windows 2000
| > > | Content-Class: urn:content-classes:message
| > > | Importance: normal
| > > | Priority: normal
| > > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > > | Newsgroups: microsoft.public.dotnet.framework.aspnet
| > > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > > | Xref: TK2MSFTNGXA01.phx.gbl
| > > microsoft.public.dotnet.framework.aspnet:134950
| > > | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| > > |
| > > | I have a series of web applications (configured as separate
applications)
| > > on
| > > | a server.
| > > |
| > > | There is a main application at the root and then several virtual
| > > directories
| > > | that are independant applications.
| > > |
| > > | I am testing an upgrade of all of the sites and have converted the
main
| > > root
| > > | site...although not necessarily fixed any issues.
| > > |
| > > | I move on instead and converted one of the virtual roots that is a
| > > seperate
| > > | app. I am getting the error below:
| > > |
| > > | Could not load file or assembly blah........
| > > |
| > > | The assembly it is referencing is not used by that application. It
is
| > > | however referenced and used by the main application that is at the
root
| > > of
| > > | the web server.
| > > |
| > > | It almost seems like the settings from the main application are
being
| > > | inherited in some manner by the separate application inthe virtual
| > > directory.
| > > |
| > > | This didn't occur in 1.1 so I'm a bit lost as to how to correct it.
I do
| > > | not want to add references to the subapplication to the assembly
because
| > > | there are multiple assemblys the main root application uses and the
| > > versions
| > > | frequently chagne due to updates. Having to manage updating
references
| > > to
| > > | the assemblies in not only th root application but all of the other
| > > separate
| > > | applications would be very time consuming and doesn't seem like it
should
| > > be
| > > | necessary.
| > > |
| > > | Sorry for the long-winded post but I wanted to make sure i was
giving all
| > > of
| > > | the details.
| > > |
| > > | Thx.
| > > |
| > >
| > >
|