Managed Extensions now obsoleted by CLI?

[J]

I've just been reading a few articles on how Managed Extensions are
now obsolete! Tough thing to hear, as I've been spending every spare
moment studying them to try to solve a problem.

I'd like to get up to speed on this as quickly as possible, and find
out how the new CLI approach relates to my current app (will it fix
anything? Make things more complex?)

It's impossible to google search for CLI, of course. Millions of
irrelevant hits. And the term CLI seems to have been re-appropriated
or extended from its earlier usage to apply to its more modern usage.

It's apparently only starting its new incarnation in Whidbey, so maybe
the term 'obsolete' is premature for Managed Extensions, but is M.E
expected to disappear quickly once Whidbey is released?

I've spotted only two books that may or may not relate:

Shared Source CLI Essentials
by David Stutz, Ted Neward, Geoff Shilling
OReilly
059600351X

[Is this worthwhile?]

And MAYBE:

The Common Language Infrastructure Annotated Standard
by James S. Miller, Susann Ragsdale, Jim Miller
Addison
0321154932

I suspect that the latter is a CLI spec in the 'older' context.

[Are there more books?]

In general, is this worth pursuing as a more versatile and
powerful solution to interop problems, or is it primarily for
cleanup of ugly and ambiguous syntax?

If the former, where can I find books and info on how I can
use it to solve interop problems involving connecting to
legacy C DLLs? I'd like to get the lay of the land to find
out whether to abandon the current attempts to use M.E.

[William DePalo [MVP VC++]]

"J" <[e-mail]> wrote in message
news:vd********************************@4ax.com...

I'd like to get up to speed on this as quickly as possible, and find
out how the new CLI approach relates to my current app (will it fix
anything? Make things more complex?)
Well, if you are not against installing beta software (I don't recommend
this for a "production" or your "main development" machine), and if you have
a broadband connection you can go here

http://lab.msdn.microsoft.com/vs2005/
It's impossible to google search for CLI, of course. Millions of
irrelevant hits. And the term CLI seems to have been re-appropriated
or extended from its earlier usage to apply to its more modern usage.
Try plugging this search string into google

CLI C++ site:msdn.microsoft.com

A quick glance at the results seems to offer promise.
It's apparently only starting its new incarnation in Whidbey, so maybe
the term 'obsolete' is premature for Managed Extensions, but is M.E
expected to disappear quickly once Whidbey is released?
Well, certainly a wise person will drop MC++ as soon as it is feasible. I'm
not sure about this but I _think_ that for those who can not drop it
immediately the old syntax will be supported. You probably should try that
out in the beta or in the shipping product as soon as it is available.
In general, is this worth pursuing as a more versatile and
powerful solution to interop problems, or is it primarily for
cleanup of ugly and ambiguous syntax?
Yes. :-) IMO, both.
If the former, where can I find books and info on how I can
use it to solve interop problems involving connecting to
legacy C DLLs? I'd like to get the lay of the land to find
out whether to abandon the current attempts to use M.E.

Until the product ships and we see what gets published, you may want to
tighten up the google search by adding Lippman (as in Stan Lippman) or
Sutter (as in Herb Sutter) to the search string above and read whatever you
can find by either of them on the subject of the CLI binding.

Regards,
Will

[Carl Daniel [VC++ MVP]]

William DePalo [MVP VC++] wrote:

"J" <[e-mail]> wrote in message

It's apparently only starting its new incarnation in Whidbey, so
maybe the term 'obsolete' is premature for Managed Extensions, but is M.E
expected to disappear quickly once Whidbey is released?

Well, certainly a wise person will drop MC++ as soon as it is
feasible. I'm not sure about this but I _think_ that for those who
can not drop it immediately the old syntax will be supported. You
probably should try that out in the beta or in the shipping product
as soon as it is available.

Yes, Whidbey will continue to support the MC++ syntax.

Command line options:

/clr - new system (C++/CLI)
/clr:oldSyntax - old syntax (MC++)

-cd

[Ioannis Vranos]

J wrote:

I've just been reading a few articles on how Managed Extensions are
now obsolete!

Deprecated. They will be replaced by C++/CLI which also provides some
more features.

Tough thing to hear, as I've been spending every spare
moment studying them to try to solve a problem.

Well it isn't such difficult switch. The __gc class is replaced by ref
class, the managed * with ^, also you get stack allocated ref types, and
deterministic destruction.
I'd like to get up to speed on this as quickly as possible, and find
out how the new CLI approach relates to my current app (will it fix
anything? Make things more complex?)

It's impossible to google search for CLI, of course. Millions of
irrelevant hits. And the term CLI seems to have been re-appropriated
or extended from its earlier usage to apply to its more modern usage.

It's apparently only starting its new incarnation in Whidbey, so maybe
the term 'obsolete' is premature for Managed Extensions, but is M.E
expected to disappear quickly once Whidbey is released?

I've spotted only two books that may or may not relate:

Shared Source CLI Essentials
by David Stutz, Ted Neward, Geoff Shilling
OReilly
059600351X

[Is this worthwhile?]

And MAYBE:

The Common Language Infrastructure Annotated Standard
by James S. Miller, Susann Ragsdale, Jim Miller
Addison
0321154932

I suspect that the latter is a CLI spec in the 'older' context.

[Are there more books?]

In general, is this worth pursuing as a more versatile and
powerful solution to interop problems, or is it primarily for
cleanup of ugly and ambiguous syntax?

Clean up and extension.

If the former, where can I find books and info on how I can
use it to solve interop problems involving connecting to
legacy C DLLs? I'd like to get the lay of the land to find
out whether to abandon the current attempts to use M.E.

C++/CLI standard is still draft and will be ratified about Match.

Some links:

Latest C++/CLI draft standard:
http://www.plumhall.com/C++-CLI%20draft%201.8.pdf

C++/CLI presentation:
http://www.accu.org/conference/prese...keynote%29.pdf

CLI official standard:
http://www.ecma-international.org/pu...s/Ecma-335.htm
And a relatively old page of mine:

http://www23.brinkster.com/noicys/cppcli.htm


--
Ioannis Vranos

[Ioannis Vranos]

Ioannis Vranos wrote:

Some links:

Latest C++/CLI draft standard:
http://www.plumhall.com/C++-CLI%20draft%201.8.pdf

C++/CLI presentation:
http://www.accu.org/conference/prese...keynote%29.pdf

CLI official standard:
http://www.ecma-international.org/pu...s/Ecma-335.htm
And a relatively old page of mine:

http://www23.brinkster.com/noicys/cppcli.htm

And some more interesting links:
http://msdn.microsoft.com/msdnmag/is...s/default.aspx

http://pluralsight.com/blogs/hsutter...0/05/2672.aspx

http://blogs.msdn.com/branbray/archi.../07/51007.aspx

http://www.accu.org/conference/prese...keynote%29.pdf

--
Ioannis Vranos