Phoenix Network Forums

What do you know about the Microsoft .net (dot net) framwork?

Are you asking or what?

btw, I have no clue

I just want to see a small statistics about how many people follow these events.

I'm in the dark, could you specify what events?

Google only comes up with the usual microsoft craptalk.

http://www.aaxnet.com/editor/edit011.html
This arcticle explains what is the .net framework in reality ,in short ,it is microsofts new idea to make people buy there products ,it states that the sotware shouldn`t be on the users computer ,it should be on a server ,read the arcticle and you`ll get the facts ,I`m curious ,what do you think about this?http://www.aaxnet.com/editor/edit011.html

DjDarkman wrote:http://www.aaxnet.com/editor/edit011.html
This arcticle explains what is the .net framework in reality ,in short ,it is microsofts new idea to make people buy there products ,it states that the sotware shouldn`t be on the users computer ,it should be on a server ,read the arcticle and you`ll get the facts ,I`m curious ,what do you think about this?http://www.aaxnet.com/editor/edit011.html

Well touch me that's old:

4-Aug-01
Microsoft.NET Gains Speed

But fair enough.

I think the .NET framework's concept is a good idea. All this common runtime jazz would make all kinds of development easier. However, the problems are:
* Any proprietary technologies that prevent open competition and code-sharing, and
* the vast differences between facilities on different platforms. For example, you won't find DirectX on many BSD systems, and good luck depending on cron on a Windows XP PC. Common runtimes for applications won't fix these massive issues for cross-platform computing.

The only advantages of .Net over scripting languages are increased ability to hide one's original source code, and the security bits, which I wouldn't trust with a peanut in some kind of peanut factory.

Someone on Wikipedia wrote:Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a call stack walk: every assembly of each method in the call stack is checked for the required permission and if any assembly is not granted the permission then a security exception is thrown.

I can only see this process chewing up a lot of CPU time.

As well as speed issues, I don't like this kind of security measure because of my experiences with Java applets, where the majority of applets that I have used are not signed. In any case, a digital signature from some random untrusted website is meaningless. There is no way to verify the trustworthiness of code coming from previously-unknown entities. It's just like verbal conversations, where there is no way to prove that a stranger who just arrived in the country has any kind of authority on a particular topic, or that he won't try to steal your kidneys if he performs surgery on you.

-pcweirdo.

PS. More jazz:
http://en.wikipedia.org/wiki/.NET_Framework#Design_goals_and_principle_features

In short.. For end users, .NET Framework is just another 20MB they have to install so some applications can work.

For developers, .NET Framework is new API. (Framework is just a part of .NET technology).

And are you confident that this is a good idea?