Yes, but it doen't matter. If I want to return an object only with data, it's possible using serialization. I want to maintain the logging functionality which requires a connection to the server. It is not a problem if I expose an assembly but the trick is doing it with a web service that has a nested interface. I need the web service for interoperability and keeping the deployment simple. I don't want to rely on the client to have a .net framework installed (or Mono for linux) to avoid the deployment of a .Net assembly. thanks
BarV
Posts
-
Connected Complex Objects In Web Services -
Connected Complex Objects In Web ServicesHello, I tried, unsuccesfully to make a webservice that returns objects with webmethods of their own, using a asp.net webservice. I need to log every action made by the client and still maintain a nested interface.;) for example: a flat regular web service interface: wsclass.getFlower returns a flower object - only with fields(not functionality). I want to return the Flower and record what the user has accessed in the object. I tried returning a webservice complient in interface to the object's instead of the object as a returning type of the getFlower. But when i ran it it raised an error about a serialization failure.:( THANX; bv
-
Changing the windows desktop background color programmaticallyThanks Sure gonna try it
-
Painting a buttonOverride the OnPaint function
-
Changing the windows desktop background color programmaticallyDoes anyone know how? thanks ;)
-
Large Heap Doesn't Compact?Thank you. ;)
-
Large Heap Doesn't Compact?Ok, so the Large Memory Heap is defragmented?
-
Large Heap Doesn't Compact?No. I relied on the Private Bytes counter in the prefmon. b.v.
-
Large Heap Doesn't Compact?I have written a C# application that uses very large objects: 1mb to 3mb, it has what seems to be a memory leak. According to microsoft and all my colleague .NET Applications DON'T leak. So I looked for an answer and came across that: "The large object heap is never compacted..." http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/DBGch02.asp[^] a quote from microsoft article about memory debugging. Isn't that means that when a memory is freed a hole is created and not handled? Is that the reason my app is leaking? Thanks b.v.