Re: Problem with MSXML and Asp.Net

[Amit]

Hello Dave,

thanks for replying.

my problem is not with Msxml. My problem is that an earlier version of a
Dll is working fine but a newer version is giving problem.
I only mentioned MSXML because it is being used in those Dll's but i personally
dont feel that it is the root cause of the problem.

Can you suggest something on this.

Thanks and Regards,

Amit.



"Dave Rothgery" <drothgery@alum.wpi.edu> wrote:
>
>"Amit" <vb.@127.0.0.1> wrote in message news:3f9e3fc9@devx7.web.devx.com...
>>
>> Hi Group,
>>
>> I am facing a little problem with my DLL's.
>>
>> I have a DLL named RealTime.Dll. This DLL uses the MSXML2.ServerXmlHttp
>object.
>> An Interop.MsXml2.Dll is automatically created by the .Net environment.
>>
>> I have one web site which references the RealTime.Dll. Earlier i had
>copied
>> the RealTime.Dll and the Interop.MsXml2.Dll to the virtual folder of the
>> Web site.
>>
>> For some reasons i made changes to my RealTime.Dll and thus again copied
>> the new versuon of the RealTime.Dll and the Interop.MsXml2.Dll but it
is
>> giving error while sending the Xml request through the ServerXmlHttp.
Also
>> if i keep the earlier versions of both the Dll's then there is no such
>error.
>
>Why are you using the MSXML object instead of System.Net.WebClient or
>System.HttpRequest? This is an ASP.NET project, correct (if not, you're
on
>the wrong newsgroup)?
>
>
>
>

[Russell Jones]

As you said you changed the realtime.dll, then probably you inadvertently
broke the COM interface contract. I suspect that either your ASP.NET code or
the other DLL or both have a reference (a GUID used to look up the DLL in
the registry) to the realtime.dll. When you recompiled the realtime DLL, the
IDE assigned a new GUID, thereby invalidating any external references. Load
both DLLs back into the IDE, make sure you update all the references,
recompile, and then redeploy the DLLs and reregister them on the server.
After doing that, update the references in your ASP.NET project and try
again.

Let us know what happens.


"Amit" <vb.@127.0.0.1> wrote in message
news:3f9fb4bf$1@devx7.web.devx.com...
>
> Hello Dave,
>
> thanks for replying.
>
> my problem is not with Msxml. My problem is that an earlier version of a
> Dll is working fine but a newer version is giving problem.
> I only mentioned MSXML because it is being used in those Dll's but i
personally
> dont feel that it is the root cause of the problem.
>
> Can you suggest something on this.
>
> Thanks and Regards,
>
> Amit.
>
>
>
> "Dave Rothgery" <drothgery@alum.wpi.edu> wrote:
> >
> >"Amit" <vb.@127.0.0.1> wrote in message
news:3f9e3fc9@devx7.web.devx.com...
> >>
> >> Hi Group,
> >>
> >> I am facing a little problem with my DLL's.
> >>
> >> I have a DLL named RealTime.Dll. This DLL uses the MSXML2.ServerXmlHttp
> >object.
> >> An Interop.MsXml2.Dll is automatically created by the .Net environment.
> >>
> >> I have one web site which references the RealTime.Dll. Earlier i had
> >copied
> >> the RealTime.Dll and the Interop.MsXml2.Dll to the virtual folder of
the
> >> Web site.
> >>
> >> For some reasons i made changes to my RealTime.Dll and thus again
copied
> >> the new versuon of the RealTime.Dll and the Interop.MsXml2.Dll but it
> is
> >> giving error while sending the Xml request through the ServerXmlHttp.
> Also
> >> if i keep the earlier versions of both the Dll's then there is no such
> >error.
> >
> >Why are you using the MSXML object instead of System.Net.WebClient or
> >System.HttpRequest? This is an ASP.NET project, correct (if not, you're
> on
> >the wrong newsgroup)?
> >
> >
> >
> >
>