New Probing Rules for 2.0?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a WinForms application that comprises files similar to this:

a.exe
b.dll
c.dll

The application is hosted on a Unix-based web server (case sensitive) and is
accessed via HTTP ("no touch") deployment. For .NET 1.1, the probing rules
required that the libraries all have upper-case "DLL" extensions, but the exe
could remain lower-case. After upgrading to .NET 2.0, however, the probing
fails, because the fusion process cannot locate "a.exe". Requesting "a.EXE"
works fine, so I'm looking for confirmation that .NET 2.0 included this
breaking change. Another byproduct of this is that the config file must also
be renamed to "a.EXE.config", instead of the original (lower-case)
"a.exe.config".

Thanks,
Rob
 
Hello Rob,

That's an interesting problem you describe there. I can't confirm or deny
the behaviour, I just want to add that on Windows the change - assuming a
change has been made - is not a breaking change, and so it might be hard
to get a confirmation of such a change as it may not have been recorded as
potentially problematic.

The other thing is, speaking from my experience running Samba servers for
Windows clients, there should be options that allow you to control case
sensitivity on the server. I wonder if it wouldn't be a lot easier to
configure the server not to be case sensitive, as Windows cannot make use
of that anyway.


Oliver Sturm
 
Oliver -

Thank you for your feedback. I understand that this isn't a breaking change
when using a Windows-based web server.

Unfortunately, I don't have such control over our production environment, so
adjusting the case-sensitivity settings isn't a practical approach.

- Rob
 
Back
Top