.NET thoughts

Posted By: spivonious | Oct 16th @ 6:56 AM
page 2 of 2
Comments: 28 | Views: 1144
#Oct 18th @ 3:06 PM
AndyC
AndyC

They really do when it comes to option apprasials, enterprise deployment, compatibility, offline installation .... etc. And, sooner or later, you end up having to deal with applications that installed the bit of .NET they use incorrectly because "it made writing our installer easier" or whatever, thereby breaking things with similar dependencies.

 

A single runtime package is a significantly less complex scenario for end users.

 

 

#Oct 18th @ 3:42 PM
exoteric
exoteric
I : Next<I>

I guess this is a rather theoretical discussion as this system does not exist, so there's no point trrying to argue over the robustness of a system that has not been realized. I think it's more a matter of making life easier for the .Net Framework guys, having less complexity to deal with. On the other hand, they have already begun introducing some coarse granuality in terms of client profiles, so we'll see what happens there going forward.

#Oct 18th @ 5:07 PM
Bass
Bass
www.s​preadfirefox.c​om/5years/

Why stop at namespaces? Smiley

#Oct 18th @ 7:13 PM
staceyw
staceyw
Before C# there was darkness...

Well, the cool thing about libraries is, you don't have to use them.  I don't see libraries as an issue.  IMO, the doc are great.

page 2 of 2
Comments: 28 | Views: 1144
Microsoft Communities