Some things will always suck in .Net, I guess

[damir_tk]

Thank you, you are very knowledgeable, I appreciate you discuss these with me in general. Just some of my thoughts on the above:

Marc Clifton wrote:

Ah, well, that's a good question, and frankly that's the reason I haven't touched WF or Entity Framework. Lack of trust, because I agree with you--a lot of what's coming out of MS is half-baked, even after the RTM.

Agree.

Marc Clifton wrote:

Because other programmers at MS use the tools/technologies available, without much thought? I see this even in non-MS devs: they reach for the "simple" solution because it's there, without thinking.

Agree.

Marc Clifton wrote:

You can. You have to provide the fully qualified path. And there's a nifty event that fires that lets you resolve an assembly when .NET can't. I use it a lot. Very useful.

Not everything is that simple really. Try this: You have your project in c:\Projects\TestForMarc, and you have other assemblies that you want to load in c:\SomeAsms. Now you do LoadFrom("c:\ComeAsms\SomeAsm.dll");, meaning that asm is in the LoadFrom context. Now you are back in your AppDomain doing stuff, you serialize that asm and deserialize it there. Now, deserialization will call Load("ASM, [...]"), or something like this, where path is not presented, and what will happen is that if ASM is not in the LoadContext then you get an exception, even though you have it loaded in your AppDomain! List out the loaded assemblies, and it is there! Now it gets even worse - you rely on all mighty AssemblyResolve to save the day, but that will automatically load any that assembly that exists in the GAC or below the AppBase - and will do that automatically. After that, you will end up with two same assemblies in your current AppDomain, none of which you will be able to cast the types from.

Marc Clifton wrote:

Erm...that's an indication you are not controlling the serialization correctly. Sounds like you're relying on the automation too much.

There are many classes and we put a lot of focus on implementing a correct design pattern to make a proper solution for every single architectural problem or enhancement. Now saying that, we use every possible way to declare, seal, inherit, override or whatever it takes to implement a correct solution for a specific problem - now throw in some need for serial

[damir_tk]

Well I guess no need to discuss different people and different customs, but also maybe you need to be mature enough to regard something ridiculous as that remark was. But this is not about that anyhow, but about you and somebody who dares to touch your God. So please, do not let me disturb you in your worshiping. End of discussion. Damir

[Shog9 0]

damir_tk wrote:

you are obviously not on top of this

Heh. You chose a library to do your work for you, don't like how it works, and chose to whine about it. What's left to understand?

Citizen 20.1.01

'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'

[Paul Conrad]

Possibly so.

"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

[BillWoodruff]

Some of us suckers are praying for the "Clifton genius" to manifest itself in the form of the "ultimate" monograph (or book) on serialization ! Not that we are unhappy now, however, as we suck up what there is to be sucked : nay, we are grateful, even if our own ignorance prevents us from fully sucking all that could be sucked from what is in our suckers :) best, Bill

"The greater the social and cultural distances between people, the more magical the light that can spring from their contact." Milan Kundera in Testaments Trahis

[Colin Angus Mackay]

:confused:

Recent blog posts: *SQL Server / Visual Studio install order *Installing SQL Server 2005 on Vista *Tip of the Day - SysInternals * Meme My Blog

[Marc Clifton]

damir_tk wrote:

I simply want to know why serialization has so many issues, why it is so limited, why so many issues on the assembly level, why remoting is so slow and should I go back to C++ binary tcp communication while this technology gets matured, and stuff like that.

Well! Thanks for the reply. Sounds like you're doing some really neat stuff and I can see how the .NET framework is getting in the way with its issues. You remind me of something I realized a while ago--the people who are writing the framework appear to be thinking only in terms of a very limited problem domain. Step outside of MS's idea of how to use various components, and you run into problems. I agree, it is frustrating, especially since they don't go back and clean up their house, but keep adding facades to hide the mess. And thank you for helping me understand the issues better! Marc

Thyme In The Country Interacx My Blog

[Alan Balkany]

I've been using XML serialization, and the SOAP format seems very verbose, cryptic, and wasteful. I can accept that, but then I constantly ran into problems. For one I found a cryptic fix on the web that worked, but it makes me uneasy that I don't understand how or why it worked. Custom serialization will definitely be more work, but it will be worth it for the reliability and sanity.

[Hamed Musavi]

Joan Murt wrote:

Between 1 and 3

Did you mean 01 and 11? :-D

"In the end it's a little boy expressing himself."    Yanni

[Joan M]

Yess! :-D

[www.tamelectromecanica.com][www.tam.cat]