Click here to Skip to main content
15,846,726 members
Home / Discussions / C#
   

C#

 
GeneralRe: MFC to C# ?? Pin
-Dy17-Oct-02 3:54
-Dy17-Oct-02 3:54 
GeneralRe: MFC to C# ?? Pin
Paul Riley17-Oct-02 4:07
Paul Riley17-Oct-02 4:07 
GeneralRe: MFC to C# ?? Pin
Michael P Butler17-Oct-02 4:24
Michael P Butler17-Oct-02 4:24 
AnswerRe: MFC to C# ?? Pin
Stephane Rodriguez.17-Oct-02 4:48
Stephane Rodriguez.17-Oct-02 4:48 
GeneralRe: MFC to C# ?? Pin
KaЯl17-Oct-02 12:14
KaЯl17-Oct-02 12:14 
GeneralRe: MFC to C# ?? Pin
Stephane Rodriguez.17-Oct-02 21:23
Stephane Rodriguez.17-Oct-02 21:23 
GeneralRe: MFC to C# ?? Pin
KaЯl18-Oct-02 0:00
KaЯl18-Oct-02 0:00 
GeneralRe: MFC to C# ?? Pin
Russell Morris17-Oct-02 13:16
Russell Morris17-Oct-02 13:16 
__Stephane Rodriguez__ wrote:
Think redistribution

This statement is only correct if you are writing an app to be distributed to end-users online. If you are shipping by CD, or if you are mainly supplying software to corporations, or are an IT division developing in-house software, this is not a concern. And I think those areas are the ones that MS has been targetting for the first wave up .NET users.

It'll be years, I think, before the .NET framework is widely distrubuted enough among the average computer user for it to make sense to develop end-user/consumer software with .NET. It's big impact in the next few years (if it has one) will be on the server side and in corporate backends.

[Edit]
--> In regards to framework versions and such (sorry, I hit the submit button instead of the reply button Blush | :O )
[/Edit]

DotNet 1.1 can be installed on the same computer as DotNet 1.0. An app written for 1.0 will run with the 1.0 framework, and an app written for 1.1 will run under the 1.1 framework.

If only the 1.1 framework is installed, the 1.0 app will try to run under the 1.1 framework. And most likely it will fail miserably, because of the imcompatibilities you point out. However, I don't see how this is any different than other upgrade scenarios, unless upgrades are never anything more than bugfixes that don't change interfaces.

If only the 1.0 framework is installed, the 1.0 app will run fine, and the 1.1 app will refuse to run.

The big problem I see with going from 1.0 to 1.1 is not getting built applications to run, it's rewriting your 1.0 apps when it turns out they are using behavior that has been altered in 1.1. This scenario worries me, of course. Our shop isn't looking at using 1.1 in the next year, as far as I know.


--
Russell Morris

"Have you gone mad Frink? Put down that science pole!"
GeneralRe: MFC to C# ?? Pin
James T. Johnson17-Oct-02 15:54
James T. Johnson17-Oct-02 15:54 
GeneralRe: MFC to C# ?? Pin
Stephane Rodriguez.17-Oct-02 21:06
Stephane Rodriguez.17-Oct-02 21:06 
Generalvirtual computers Pin
plextoR16-Oct-02 10:11
plextoR16-Oct-02 10:11 
GeneralRe: virtual computers Pin
Philip Fitzsimons17-Oct-02 1:17
Philip Fitzsimons17-Oct-02 1:17 
GeneralRe: virtual computers Pin
JasonSmith18-Oct-02 14:19
JasonSmith18-Oct-02 14:19 
GeneralRe: virtual computers Pin
Philip Fitzsimons20-Oct-02 23:58
Philip Fitzsimons20-Oct-02 23:58 
GeneralTreeView source code Pin
Patrick Lassalle16-Oct-02 6:10
Patrick Lassalle16-Oct-02 6:10 
GeneralRe: TreeView source code Pin
Stephane Rodriguez.16-Oct-02 6:15
Stephane Rodriguez.16-Oct-02 6:15 
GeneralRe: TreeView source code Pin
David Stone16-Oct-02 13:18
sitebuilderDavid Stone16-Oct-02 13:18 
GeneralRe: TreeView source code Pin
Stephane Rodriguez.16-Oct-02 20:09
Stephane Rodriguez.16-Oct-02 20:09 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.