Y
Y2K
First.. I sincerely appreciate any assistance in resolving this.
I've searched the entire PC for assembly.adaptive.xsd, and it's non
existent. Here's the problem:
I've published a standard VB.Net 2005 application to the IIS 5.0
server. I have three PCs which run my online-only application fine,
and two that give the error below right after the confirmation to
install the application:
Event ID: 5000,
Source: .NET Runtime 2.0 Error
Description: EventType clr20r3, P1 TestApp.exe, P2 1.0.2273.28313, P3
44233476, P4 testApp, P5 1.0.2273.28313, P6 44233476, P7 d, P8 c6, P9
system.invalidoperationexception, P10 NIL.
The TestApp.exe is a very simply application, so I don't think that's
the root of the problem, but I could be wrong. The subject to this
topic is where I think the problem lies, because in my manifest file, I
see..
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1
assembly.adaptive.xsd" manifestVersion="1.0"
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
xmlns="urn:schemas-microsoft-com:asm.v2"
xmlns:asmv1="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<asmv1:assemblyIdentity name="RLXtestBOM.exe" version="1.0.0.16"
publicKeyToken="0000000000000000" language="neutral"
processorArchitecture="msil" type="win32" />
And.. assembly.adaptive.xsd is underlined as "could not find".
The application builds and publishes without any errors. All PCs are
XP Pro SP2. What I have not done is update the .Net 2.0 Framework on
all PCs, and will try that next.
Again, thanks for anything.
Y2K
I've searched the entire PC for assembly.adaptive.xsd, and it's non
existent. Here's the problem:
I've published a standard VB.Net 2005 application to the IIS 5.0
server. I have three PCs which run my online-only application fine,
and two that give the error below right after the confirmation to
install the application:
Event ID: 5000,
Source: .NET Runtime 2.0 Error
Description: EventType clr20r3, P1 TestApp.exe, P2 1.0.2273.28313, P3
44233476, P4 testApp, P5 1.0.2273.28313, P6 44233476, P7 d, P8 c6, P9
system.invalidoperationexception, P10 NIL.
The TestApp.exe is a very simply application, so I don't think that's
the root of the problem, but I could be wrong. The subject to this
topic is where I think the problem lies, because in my manifest file, I
see..
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1
assembly.adaptive.xsd" manifestVersion="1.0"
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
xmlns="urn:schemas-microsoft-com:asm.v2"
xmlns:asmv1="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<asmv1:assemblyIdentity name="RLXtestBOM.exe" version="1.0.0.16"
publicKeyToken="0000000000000000" language="neutral"
processorArchitecture="msil" type="win32" />
And.. assembly.adaptive.xsd is underlined as "could not find".
The application builds and publishes without any errors. All PCs are
XP Pro SP2. What I have not done is update the .Net 2.0 Framework on
all PCs, and will try that next.
Again, thanks for anything.
Y2K