Common misconceptions of .NET?

  • (2 Pages)
  • +
  • 1
  • 2

27 Replies - 6514 Views - Last Post: 04 September 2014 - 01:36 PM

#16 atraub  Icon User is offline

  • Pythoneer
  • member icon

Reputation: 759
  • View blog
  • Posts: 2,010
  • Joined: 23-December 08

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 07:16 AM

Misconception: You have to buy Visual Studio in order to write .net programs. (Feel free to expand on this one)
Was This Post Helpful? 0
  • +
  • -

#17 AdamSpeight2008  Icon User is offline

  • MrCupOfT
  • member icon


Reputation: 2263
  • View blog
  • Posts: 9,468
  • Joined: 29-May 08

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 07:40 AM

I thought this thread was about dispelling misconception about .net.
Just because a non vb.net coder has misconceptions, or doesn't understand it, because of its look.
You have my sympathises baavgai but don't judge a language solely on its syntax and the way it looks, which you seem to be doing.

I ask about your claims about class design decisions that were a bad idea.
I wanted your rationale discussion not diatripe or a rant. So could learn from it.

I don't understand the look of functional languages, doesn't mean functional languages are inherently wrong.
Some aspect of my program have a functional slant to them. I understand the rationale behind the functional idea.

Just because a language doesn't have curly brace and semi-colons equate it to being crap. Take LISP or FORTH.

This post has been edited by AdamSpeight2008: 08 February 2011 - 07:47 AM

Was This Post Helpful? -1
  • +
  • -

#18 eclipsed4utoo  Icon User is offline

  • Not Your Ordinary Programmer
  • member icon

Reputation: 1524
  • View blog
  • Posts: 5,960
  • Joined: 21-March 08

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 07:50 AM

View Postatraub, on 08 February 2011 - 10:16 AM, said:

Misconception: You have to buy Visual Studio in order to write .net programs. (Feel free to expand on this one)


The Express versions of Visual Studio are free. You can use SharpDevelop, which is free. You could also use MonoDevelop, which is also free.

So no, you don't have to buy Visual Studio to write .Net applications.
Was This Post Helpful? 0
  • +
  • -

#19 atraub  Icon User is offline

  • Pythoneer
  • member icon

Reputation: 759
  • View blog
  • Posts: 2,010
  • Joined: 23-December 08

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 08:04 AM

No one has said it directly yet (though they have implied it a few times).

Misconception: Server side .net stuff can only run on windows based OS's.
Was This Post Helpful? 0
  • +
  • -

#20 Sergio Tapia  Icon User is offline

  • D.I.C Lover
  • member icon

Reputation: 1253
  • View blog
  • Posts: 4,168
  • Joined: 27-January 10

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 08:52 AM

Misconception: If you use .NET your users have to download HUGE framework installer!
Truth: .Net comes preinstalled in the newer versions of Windows right out of the box.
Was This Post Helpful? 0
  • +
  • -

#21 Curtis Rutland  Icon User is online

  • (╯□)╯︵ (~ .o.)~
  • member icon


Reputation: 4496
  • View blog
  • Posts: 7,848
  • Joined: 08-June 10

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 08:56 AM

Version is important though, Sergio. For instance, I just installed Server 2k8R2 on a computer at home, and when I went to install MVC3 on it, it informed me that I didn't have .NET 4.0. I believe all systems currently come with .NET 3.5 on them.
Was This Post Helpful? 0
  • +
  • -

#22 baavgai  Icon User is offline

  • Dreaming Coder
  • member icon

Reputation: 5846
  • View blog
  • Posts: 12,705
  • Joined: 16-October 07

Re: Common misconceptions of .NET?

Posted 08 February 2011 - 09:04 AM

View PostAdamSpeight2008, on 08 February 2011 - 09:40 AM, said:

but don't judge a language solely on its syntax and the way it looks, which you seem to be doing.


Of course. You judge a language on what it can do. But anything VB.NET can do, any other .NET language can do. Given this, when choosing a .NET language, my only two serious considerations are support and syntax. The best supported languages in .NET are VB.NET and C#. The choice is clear.

Misconception: all the languages supported in .NET are supported equally. It's sadly not the case, C# and VB.NET are the best supported. Even the mutant C++.NET is quirky, though it's an integral part of VS. Things like IronPython can be even more eccentric. Given a Visual Studio choice, I'd stick with the biggies. Personally, I'd choose the less verbose one. ;)
Was This Post Helpful? 2
  • +
  • -

#23 TestSubjectRC2  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 2
  • Joined: 29-January 11

Re: Common misconceptions of .NET?

Posted 16 February 2011 - 01:34 PM

modi123_1 said:

Q: VB.NET is a toy language never used in the real world!

A: Some of the most successful software was written with languages you might not expect. One of the best top-scrolling video games ever created, Tyrian, was written in Pascal. My favorite DAW (Digital Audio Workstation), FL Studio, is written in Delphi. "Real world" application is based on results. If you can get it done, how many people are concerned with what you used?

atraub said:

Misconception: You have to buy Visual Studio in order to write .net programs. (Feel free to expand on this one)

Now that's interesting. I didn't know this wasn't true until I read this thread.

This post has been edited by TestSubjectRC2: 16 February 2011 - 01:37 PM

Was This Post Helpful? 0
  • +
  • -

#24 atraub  Icon User is offline

  • Pythoneer
  • member icon

Reputation: 759
  • View blog
  • Posts: 2,010
  • Joined: 23-December 08

Re: Common misconceptions of .NET?

Posted 16 February 2011 - 01:36 PM

I believe in 2004, VB was the most used language in the field (I read something to that effect in Code Complete)
Was This Post Helpful? 0
  • +
  • -

#25 Curtis Rutland  Icon User is online

  • (╯□)╯︵ (~ .o.)~
  • member icon


Reputation: 4496
  • View blog
  • Posts: 7,848
  • Joined: 08-June 10

Re: Common misconceptions of .NET?

Posted 16 February 2011 - 01:53 PM

Quote

Misconception: You have to buy Visual Studio in order to write .net programs. (Feel free to expand on this one)


MonoDevelop (technically not .NET, it's Mono)
SharpDevelop (open source .NET IDE)
Visual Studio Express (my personal favorite. It's VS lite, only missing a few features that amateur developers rarely use anyway)

Of course, there's always csc.exe and vbc.exe (the command line compilers), if you're a masochist.

This post has been edited by insertAlias: 16 February 2011 - 01:55 PM

Was This Post Helpful? 0
  • +
  • -

#26 modi123_1  Icon User is online

  • Suitor #2
  • member icon



Reputation: 9267
  • View blog
  • Posts: 34,760
  • Joined: 12-June 08

Re: Common misconceptions of .NET?

Posted 16 February 2011 - 01:54 PM

That or get the Express Edition.
Was This Post Helpful? 0
  • +
  • -

#27 ryios  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 2
  • Joined: 13-April 14

Re: Common misconceptions of .NET?

Posted 04 September 2014 - 01:34 PM

You can't load a .Net DLL in a native process. .Net is managed, all MSIL, not X86, they don't cross like that, It's a virtual engine based language... etc etc..

Misconception!!

Dot Net compiles to MSIL: True, However,

.Net Compiles to PE Format Compliant files just like any other windows dll, sys driver, or dll. When .Net Framework came out PE Format was extended to include a new 1/0 value that indicates whether it is a .Net assembly or not.

When the windows loader is asked to load an EXE with that flag set, it use the CLR Hosting API to JIT compile it to X86 (converting the MSIL to x86 on windows. Once it's been JITTED to x86, windows loads it just like any other native exe, and it loads it's JITTED Dll's just like any normal com or dynamic dll...

What this means is that once a .Net EXE is running as a process, it's as native as any other process, but includes access to all the referenced parts of the .net framework.

So, you can load a .Net DLL in a native process. All it requires is getting the native process to LOAD the .Net Framework code. Which can be done by injecting a dynamic dll into the process that uses the CLR Hosting ASI to start the .Net Framework. Once the Framework is loaded you can use Assembly.Load to dynamically load .net dll's into it.

The reverse is true for .net, you CAN inject dynamic dll's into Processes built on the .Net Framework.

The misconception is people think .Net runs in a virtual EXE like Java, when that's not the case. .Net Processes run as standard native win32/64 processes, decicated process, that run as themselves, not on some special exe like JAVA code does.
Was This Post Helpful? 0
  • +
  • -

#28 modi123_1  Icon User is online

  • Suitor #2
  • member icon



Reputation: 9267
  • View blog
  • Posts: 34,760
  • Joined: 12-June 08

Re: Common misconceptions of .NET?

Posted 04 September 2014 - 01:36 PM

Let's be a little conscientious about dredging up topics from 2011, and avoid doing that. Thanks.
Was This Post Helpful? 0
  • +
  • -

  • (2 Pages)
  • +
  • 1
  • 2