R
Richard
In my app I serialize to save some data. I have run into the problem where
the temporary dll created and compiled on the fly is not found and my app
fails. This appears to be related to doing the serialzation in response to
the user logging off and my app getting the message to shutdown. The app
saves config and works fine most of the time but fails sometimes when it
can't find the temp dll.
Now I have modified my VS2005 project to use sgen to build the serialization
dll at compile time in the hopes of avoiding the on the fly compile. The sgen
runs and creates "myfile.xmlserializers.dll" and this looks fine. However,
when the app runs and its time to serialize, my app tries to load
"myfile.xmlserializers.-10928561.dll" and since the file was created as
myfile.xmlserializers.dll, the bind fails. If I rename the dll to inlcude the
funny number, the dll loads but then the bind fails because the name inside
the dll apparently does not have that number.
Can anyone tell me what is going on here? What is that number that Vb.net is
attaching to the serializer dll name that fails to match the physicall dll
name? If vb wants to use this name, why does sgen not appear to know about
it? Why in extensive online discussions of this technique, is this strange
dll name not mentioned (except for one case where another person was getting
this strange dll name but it did not seem to pose a problem as that person
was discussing a problem different than not binding)?
Help!
the temporary dll created and compiled on the fly is not found and my app
fails. This appears to be related to doing the serialzation in response to
the user logging off and my app getting the message to shutdown. The app
saves config and works fine most of the time but fails sometimes when it
can't find the temp dll.
Now I have modified my VS2005 project to use sgen to build the serialization
dll at compile time in the hopes of avoiding the on the fly compile. The sgen
runs and creates "myfile.xmlserializers.dll" and this looks fine. However,
when the app runs and its time to serialize, my app tries to load
"myfile.xmlserializers.-10928561.dll" and since the file was created as
myfile.xmlserializers.dll, the bind fails. If I rename the dll to inlcude the
funny number, the dll loads but then the bind fails because the name inside
the dll apparently does not have that number.
Can anyone tell me what is going on here? What is that number that Vb.net is
attaching to the serializer dll name that fails to match the physicall dll
name? If vb wants to use this name, why does sgen not appear to know about
it? Why in extensive online discussions of this technique, is this strange
dll name not mentioned (except for one case where another person was getting
this strange dll name but it did not seem to pose a problem as that person
was discussing a problem different than not binding)?
Help!