|
That is likely because the PosDamAx object (which I am guessing is an ActiveX control) is 32 bit only. All of your projects in your solution must be set to compile as x86 and not as AnyCPU.
|
|
|
|
|
I have windows form , which contains treeview.
When i drag node and drop on windows explorer, i want event which will give me windows exploer path. Where I actually end node drag.
Does any body have solution for same.
|
|
|
|
|
|
I have Treeview on form, Tree view contain differnt nodes.
|
|
|
|
|
Somnath T Avhad wrote: I have Treeview on form, Tree view contain differnt nodes.
I have a treeview with different nodes, too. The world is so small!
------------------------------
Author of Primary ROleplaying SysTem
How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.
|
|
|
|
|
even on intranet, sending objects back and forth eventually you'd run into deserialization exception and to handle this client must resend the request, that's how we deal with this.
- what's your experience on this?
dev
|
|
|
|
|
devvvy wrote: eventually you'd run into deserialization exception The first thing to do is investigate what exception is thrown and why.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Yes - but haven't you encountered the scenario you're wiring pretty same object but every so often deserialization exceptions thrown?
dev
|
|
|
|
|
devvvy wrote: but haven't you encountered the scenario you're wiring pretty same object but every so often deserialization exceptions thrown? No; what is your issue?
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
|
devvvy wrote: solution here And a fairly obvious one. No wonder I never came across the problem.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
devvvy wrote: even on intranet, sending objects back and forth eventually you'd run into deserialization exception and to handle this client must resend the request, that's how we deal with this.
Not due to network-errors. What does the exception say?
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
blows up when System.Runtime.Serialization.DataContractSerializer attempts to ReadObject(byte[])
this said, one other suggested it could be threading issue... not sure but easy enuf to test out (... testing now...)
dev
|
|
|
|
|
I deal with it by sending messages, not objects. And of course insuring that I read the message correctly.
|
|
|
|
|
it's actually object graphs -
dev
|
|
|
|
|
Doesn't matter.
Sockets only send data. So anyway you want to send an 'object' it is still data.
And thus one sends a message not data, where the message contains data.
|
|
|
|
|
|
Is the application multi-threaded?
If the answer is yes, then you probably have a synchronization problem (not having synchronization at all is a big problem).
Considering you are using TCP/IP, I can't say about any other problem. My serialization works everytime... and I have some servers that use serialization for all their tasks, multi-threaded, and they work for years without receiving serialization exceptions.
|
|
|
|
|
|
At my company I am told to get this C# 2008 application to work that has been 'stored away' for a year. The programmer who wrote the application is no longer working for this company.
I have the following 3 references that need to resolved for ths application to work correctly:
1. I am missing a reference to the common.logging.dll. I clicked under references and selected the .net and com tabs. I did not find the common.logging.dll.
Is this some .net feature that I need to add to this solution file? If so, can you tell me how to locate this feature and add it to my solution file? If not, can you tell me where I can locate the common.logging.dll and how to attach the reference to my solution file?
2. My other 2 references are the names of 2 of the project files that are part of the applicable solution file. Thus I am thinking that I need to rebuild each of the two project files separately from the entire solution file to obtain the required dll files. To obtain the applicable dlls, I am thinking that I need to obtain a reference to each file in the bin/debug or bin/release folders?
Is obtaining the applicable dlls from the bin/debug or bin/release folders a good idea or not?
Can you tell me if what I am planning to do is correct and/or what change(s) you think I should make?
|
|
|
|
|
You need to locate common.logging.dll and add that to your project.
It might be a third party dll.
|
|
|
|
|
Would you have an idea of where I can obtain the common.loggin.dll?
|
|
|
|
|
Check your repository. You might find the source code for this dll lying around somewhere.
|
|
|
|
|
With a name like common.logging, I suspect it's a project that is internal to the company.
|
|
|
|
|
For the two references that are references to other projects within the solution, remove the references to the .dll and add project references. That will make the compilation tree and dependency checking work properly.
You will have to find common.logging.dll. That sounds like it could also be part of the solution, or a common library that's available in your company. It seems unlikely that a third party would release software under the assembly name prefix 'common' so it's probably internal.
|
|
|
|