Microsoft not recomenting managed developement. isn't it ?
-
Microsoft still using Win32, MFC and COM technologies in their latest products,In my knowledge almost all the products. I am really surprised about why they are not using managed code for their products ? :omg:
-
I agree with that,but in their latest products like visual studio 2005 and above...? Also Microsoft already stated that they have no plans to release a managed DirectX support. :confused: :confused:
Visual studio 2010 uses .net (WPF), Visual 2005 is not the LATEST.
Rajeev K R Pala wrote:
Microsoft already stated that they have no plans to release a managed DirectX support
They use WPF layer above directX. Please do some research before coming out the statements that are completely incorrect.
Two heads are better than one.
-
Rajeev K R Pala wrote:
Microsoft still using Win32, MFC and COM technologies in their latest products
False.
Rajeev K R Pala wrote:
I am really surprised about why they are not using managed code for their products ?
They are but not all of them. Image rewriting the Office Suite in .net it would take years to code and test, they can't afford to do that.
Two heads are better than one.
Norm .net wrote:
Image rewriting the Office Suite in .net it would take years to code and test
and centuries to run... :rolleyes:
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Windows is not a managed OS. Therefore, new OS APIs must not be managed if they are to be used by... the OS! Remember, one of the big goals for .NET was to make using native APIs from a managed environment easier.
-
I agree with that,but in their latest products like visual studio 2005 and above...? Also Microsoft already stated that they have no plans to release a managed DirectX support. :confused: :confused:
That would be because they are steering people towards XNA. Oh, surprise surprise, XNA is available as managed code. I do agree that in their latest products, like Windows 3.11 and Quick C, they aren't using .NET.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
That would be because they are steering people towards XNA. Oh, surprise surprise, XNA is available as managed code. I do agree that in their latest products, like Windows 3.11 and Quick C, they aren't using .NET.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Shog9 wrote:
Remember, one of the big goals for .NET was to make using native APIs from a managed environment easier
And it worked, I don't think I could go back to my C++/Win32/MFC/COM days again :)
Two heads are better than one.
But i think in a different way. If we have deep knowledge about a subject then whats the need of a mediator like CLR to execute. It should only cause some performance issues when we doing some system side programming like video related works. If we are using managed code for this purpose we must need to work under CLR. So i think Microsoft looking for performance rather than look and feel... :laugh: :laugh:
-
Microsoft still using Win32, MFC and COM technologies in their latest products,In my knowledge almost all the products. I am really surprised about why they are not using managed code for their products ? :omg:
-
Because managed code is for babies. Real men code in C and C++. :)
Morality is indistinguishable from social proscription
I don't know ... But the things are going on that way.... ;)
-
Norm .net wrote:
Image rewriting the Office Suite in .net it would take years to code and test
and centuries to run... :rolleyes:
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Smacks of WPF VS2010.
-
Windows is not a managed OS. Therefore, new OS APIs must not be managed if they are to be used by... the OS! Remember, one of the big goals for .NET was to make using native APIs from a managed environment easier.
And in doing so they have made accessing the hardware of the machine a nightmare. USB? GPIO pins? X|
-
Because managed code is for babies. Real men code in C and C++. :)
Morality is indistinguishable from social proscription
Every problem is a nail, and every solution a hammer for you, huh?
Software Zen:
delete this; -
Visual studio 2010 uses .net (WPF), Visual 2005 is not the LATEST.
Rajeev K R Pala wrote:
Microsoft already stated that they have no plans to release a managed DirectX support
They use WPF layer above directX. Please do some research before coming out the statements that are completely incorrect.
Two heads are better than one.
Norm .net wrote:
Visual studio 2010 uses .net (WPF),
Which we pay dearly for. In VS2008, the whole VS architecture was completely COM-based, shining through at every corner of writing addins. I never found any mention that that was replaced.
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server. -
Every problem is a nail, and every solution a hammer for you, huh?
Software Zen:
delete this;