RE: Where has WMSDefines Gone in SP2???????

Are you able to compile fine? If yes, which version of VS are you using? My
situation seems to be worse

In VS 2003 .NET C# (even without the additional defines) when I try to
compile, I get "Could not bind to dependency interop_msxml.dll"

---------------------------------------------------------
What's worse, I can't even add the new version of
Microsoft.WindowsMediaServices.dll as a reference to my VS project. I get the
following error message

"Trying to add that as reference:
Not a COM component or assembly!!!"
---------------------------------------------------------

And if I try to register my previously built DLL, I get
C:\WINDOWS\system32\windows media\server>regasm myPlugin.dll /tlb /verbose

Microsoft (R) .NET Framework Assembly Registration Utility 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
RegAsm error: The format of the file 'Microsoft.WindowsMediaServices' is
invalid
..



Any ideas?

Thanks



"AndyMc" wrote:

Thanks for that, it will give me a start.

"javatopia" wrote:

I migrated the header definitions from the Platform SDK over to some C# code.
These definitions are the ones that I use most often. It's not complete,
sorry, but it will get you started I bet:

public const string WMS_SERVER_EVENT_LOG = "WMS_SERVER_EVENT_LOG";
public const int WMS_SERVER_EVENT_LOG_ID = 17;
public const string WMS_USER_AUTHENTICATOR = "WMS_USER_AUTHENTICATOR";
public const int WMS_USER_AUTHENTICATOR_ID = 7;
public const string WMS_USER_NAME = "WMS_USER_NAME";
public const int WMS_USER_NAME_ID = 3;
public const string WMS_PRESENT_REQUEST_NAME =
"WMS_PRESENT_REQUEST_NAME";
public const int WMS_PRESENT_REQUEST_NAME_ID = 5;
public const string WMS_PRESENT_PHYSICAL_NAME =
"WMS_PRESENT_PHYSICAL_NAME";
public const int WMS_PRESENT_PHYSICAL_NAME_ID = 4;
public const string WMS_PRESENT_ORIGINAL_REQUEST_NAME =
"WMS_PRESENT_ORIGINAL_REQUEST_NAME";
public const int WMS_PRESENT_ORIGINAL_REQUEST_NAME_ID = 17;
public const string WMS_PRESENT_ORIGINAL_PHYSICAL_NAME =
"WMS_PRESENT_ORIGINAL_PHYSICAL_NAME";
public const int WMS_PRESENT_ORIGINAL_PHYSICAL_NAME_ID = 16;
public const string WMS_USER_IP_ADDRESS_STRING =
"WMS_USER_IP_ADDRESS_STRING";
public const int WMS_USER_IP_ADDRESS_STRING_ID = 5;
public const string WMS_USER_AGENT = "WMS_USER_AGENT";
public const int WMS_USER_AGENT_ID = 1;
public const string WMS_USER_REFERER = "WMS_USER_REFERER";
public const int WMS_USER_REFERER_ID = 26;

I put these into one of my utility classes and replaced WMSDefines.XXX with
MyUtility.XXX - it compiled of course, but I have not tried deploying it yet.
--
Jacob W Anderson
---
http://www.beyond-ordinary.com
http://www.extremeplannerlive.com
---
If you think it''''s expensive to hire a professional to do the job, wait
until you hire an amateur.



"AndyMc" wrote:

FYI, I have logged a support call with Microsoft, SRQ070802600437, who have
confirmed that this is a bug and this is the latest reply that I have had
back this morning

' just wanted to inform you that the Product Group has the work item
assigned and they are working on the problem.
I check the status regularly. Please note that as this fix needs a lot of
testing and it takes some time to get it delivered.
As I mentioned I will inform you on the news as this is in the right phase.'

When I get anymore news I will post it here. By the following are a couple
work arounds that were suggested;

' would like to inform you that I applied some tests with the custom plug-in
that is using the previous version of the mentioned DLL. (So I just
referenced the previous version of the DLL from the plug-in code and did not
changed the DLL itself that is present on the system currently.)

According to my tests it should be working but we cannot guarantee that this
won’t cause any issues that did not come up during the tests.

During a discussion with my colleagues we found that another temporary
workaround could be copying the missing code to the custom plug-in code. This
would avoid referencing a previous DLL. From this perspective this is a more
safe solution.

To make it clear these are only temporary solutions as we want to fix the
problem and get a supported DLL on the system.

Regarding this: I have already sent the template to my colleague in the US.
Now he will continue this with raising the work item with the Product Group.

In case there are some remaining question from our side I will let you know.'


"javatopia" wrote:

More fun. I did find the WMS DLL in the Platform SDK for Windows 2003 SP2,
but it's version 9.0.0.3693, which we all already have. If you bind on that
DLL and try to deploy to a running SP2 system, it will not work.

Windows 2003 SP2 comes with WMS DLL version 9.1.1.3842, which does not have
a public WMSDefines class.

Help??
--
Jacob W Anderson
---
http://www.beyond-ordinary.com
http://www.extremeplannerlive.com
---
If you think it''''s expensive to hire a professional to do the job, wait
until you hire an amateur.



"AndyMc" wrote:

This is getting really frustrating, as if I have not had enough problems with
MMS and trying to create a custom plugin, now MS throw another curve ball at
me just as I am starting to get somewhere. On my development machine, in the
SDK/include folder I am using Micrsoft.WindowsMediaServices.dll v9.0.0.3693.
On my Windows Media Server the same file is v9.1.1.3842. No problem I think,
I'll just copy the newer version over to my development machine and compile
with that. This is where the fun starts, now using the newer version I find
that 'WMSDefines' no longer exists, it is missing from the newer DLL!!!
D'oh!!! I have no idea where this has been moved to or even if there is a
replacement that I should be using, does anybody have any ideas on how to
solve this? I am programming using C#.


.

Relevant Pages

  • Re: Where to place class file
    ... not sure but never heard about this automatic reference thing. ... copy local is true then the DLL is copied into the bin directory. ... Now When I compile it and place the dll in the bin and ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Program does not invoke methods of ActiveX-DLL
    ... load and compile one thing at a time. ... > declared in that dll. ... If you have a dll called DLLA and another called DLLB, ... reference DLLB if DLLB doesn't contain a reference to DLLA... ...
    (microsoft.public.vb.com)
  • Re: VB.NET 2002 IDE Failing to update local dependencies
    ... Remove the reference to the old DLL ... Attempt to save and compile ... > Hi Nick, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VBA and VSTO
    ... If you compile in VB6 with Global MultiUse than all you have to do is set a reference in Excel to your dll via Tools, References and you can access your functions in the dll directly. ... You will have to register the dll as well with Windows with Regsvr32, but that can be done quite simply in VBA. ...
    (microsoft.public.excel.programming)
  • Re: HOW CAN I OPEN A COM PROJECT COMPILED IN VS2005, IN VS2003?
    ... I keep getting the .exe output when I compile in the VC7. ... the General Configuration Type to be .dll in the Project Property. ... Microsoft MVP, MCSD ... instead create my own folders for file grouping... ...
    (microsoft.public.win32.programmer.ole)