H
harsha.ramesh
Hi All,
I am a newbie with .NET. I am trying to get some RTC integration to
work. So basically, i have the following structure:
1. I have imported the TLB file relating to the rtcdll.dll (which is a
unmanaged dll file), thereby creating a managed dll file.
2. I refer to this dll file in my C# project.
Everytime i run the project, i keep bumping into some exceptions, which
i realized was caused because the wrong dll file was being loaded up!
So, basically i have around three difference versions of the rtcdll
file (installed by what operations -- i have no clue)
Then next thing i do is place a <my-app-name>.exe.manifest file which
is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="x86"
name="Microsoft.Windows.Networking.RTCPresence"
type="win32"
/>
<description>RTC Presence</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Networking.RtcDll"
version="5.2.1002.3"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>
When i use this manifest file, everything works like a charm.
But
then VS 2005 does not have an option of creating a manifest file.. So,
i am lost again.
Now, i happened to read about config files, and i was wondering, how
could i transform the above manifest information into the config file.
Eventually, i will need all this information bundled into the dll file
that i am generating, which will inturn be refered by some webservices.
Now, can someone please tell me what is the difference between config
and manifest file? Next, is it possible to use the config file in place
of the manifest file?
I am totally lost about .NET and I have no clue on getting all these
items tied up together. I am really looking forward to some
enlightening questions.
regards,
My Env:
..NET 2.0 / VS 2005
I am a newbie with .NET. I am trying to get some RTC integration to
work. So basically, i have the following structure:
1. I have imported the TLB file relating to the rtcdll.dll (which is a
unmanaged dll file), thereby creating a managed dll file.
2. I refer to this dll file in my C# project.
Everytime i run the project, i keep bumping into some exceptions, which
i realized was caused because the wrong dll file was being loaded up!
So, basically i have around three difference versions of the rtcdll
file (installed by what operations -- i have no clue)
Then next thing i do is place a <my-app-name>.exe.manifest file which
is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="x86"
name="Microsoft.Windows.Networking.RTCPresence"
type="win32"
/>
<description>RTC Presence</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Networking.RtcDll"
version="5.2.1002.3"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>
When i use this manifest file, everything works like a charm.
Butthen VS 2005 does not have an option of creating a manifest file.. So,
i am lost again.
Now, i happened to read about config files, and i was wondering, how
could i transform the above manifest information into the config file.
Eventually, i will need all this information bundled into the dll file
that i am generating, which will inturn be refered by some webservices.
Now, can someone please tell me what is the difference between config
and manifest file? Next, is it possible to use the config file in place
of the manifest file?
I am totally lost about .NET and I have no clue on getting all these
items tied up together. I am really looking forward to some
enlightening questions.
regards,
My Env:
..NET 2.0 / VS 2005