Are there any plans to support C# modules in VS.NET in a future version.
modules in VS.NET.
Collapse
This topic is closed.
X
X
-
Peter RillingTags: None -
Miha Markic
Re: modules in VS.NET.
Hi Peter,
What's a module?
--
Miha Markic - RightHand .NET consulting & development
miha at rthand com
"Peter Rilling" <peter@nospam.r illing.net> wrote in message
news:OsDslzx4DH A.2136@TK2MSFTN GP12.phx.gbl...[color=blue]
> Are there any plans to support C# modules in VS.NET in a future version.
>
>[/color]
-
Robert Jacobson
Re: modules in VS.NET.
Do you mean like a VB.Net module? If so, probably not. A VB.Net module is
really just a sealed(NotInher itable) class with static (Shared) members, so
there isn't any particular need for the "module" syntax in C#. For example,
these code snippets are identical:
Module Module1
Sub Main()
DoSomething()
End Sub
End Module
sealed class Module1 {
static void Main() {
DoSomething();
}
}
For details:
"Visual Basic .NET Internals"
http://msdn.microsoft.com/library/de...tinternals.asp
"Peter Rilling" <peter@nospam.r illing.net> wrote in message
news:OsDslzx4DH A.2136@TK2MSFTN GP12.phx.gbl...[color=blue]
> Are there any plans to support C# modules in VS.NET in a future version.
>
>[/color]
Comment
-
Daniel O'Connell
Re: modules in VS.NET.
Actually, if memory serves, C# is supposed to gain this feature at some
point(I don't know if it'll be 2.0 or longhorn time frame however). The
syntax was supposed to be something like
public static class Class1
{
public static void Class1Method()
{
}
}
I forget where I read that, and it may not be true any longer, but it seems
to me that it was being added.
On the other hand, if the op is talking about netmodules, I also recall
reading about an addition to whidbey that adds easier use of them, but again
I don't know where I read that or if its valid offhand.
"Robert Jacobson" <rjacobson_at_o ddpost_com@nosp am.com> wrote in message
news:efVV5gy4DH A.1636@TK2MSFTN GP12.phx.gbl...[color=blue]
> Do you mean like a VB.Net module? If so, probably not. A VB.Net module[/color]
is[color=blue]
> really just a sealed(NotInher itable) class with static (Shared) members,[/color]
so[color=blue]
> there isn't any particular need for the "module" syntax in C#. For[/color]
example,[color=blue]
> these code snippets are identical:
>
> Module Module1
>
> Sub Main()
> DoSomething()
> End Sub
>
> End Module
>
>
> sealed class Module1 {
>
> static void Main() {
> DoSomething();
> }
>
> }
>
>
> For details:
> "Visual Basic .NET Internals"
>[/color]
http://msdn.microsoft.com/library/de...tinternals.asp[color=blue]
>
>
> "Peter Rilling" <peter@nospam.r illing.net> wrote in message
> news:OsDslzx4DH A.2136@TK2MSFTN GP12.phx.gbl...[color=green]
> > Are there any plans to support C# modules in VS.NET in a future version.
> >
> >[/color]
>
>[/color]
Comment
-
Lawrence Oluyede
Re: modules in VS.NET.
"Peter Rilling" <peter@nospam.r illing.net> writes:
[color=blue]
> Are there any plans to support C# modules in VS.NET in a future version.[/color]
I don't know if in the future VS.NET will be able to compile
modules but... maybe yes.
bye
--
Lawrence
Comment
-
Lawrence Oluyede
Re: modules in VS.NET.
"Miha Markic" <miha at rthand com> writes:
[color=blue]
> Hi Peter,
>
> What's a module?[/color]
c:\>csc /nologo /t:module hello.cs
c:\>dir
hello.netmodule
Modules are assemblies without manifest, allowing you to merge modules created
in different languages within a single assembly
--
Lawrence
Comment
-
Peter Rilling
Re: modules in VS.NET.
I am not referring to the VB.NET "module" construct but rather the
capability to compile code to a .netmodule file. This can be done on the
CSC compiler, but not in VS.NET. VS.NET only supports executables and
assembly libraries.
"Robert Jacobson" <rjacobson_at_o ddpost_com@nosp am.com> wrote in message
news:efVV5gy4DH A.1636@TK2MSFTN GP12.phx.gbl...[color=blue]
> Do you mean like a VB.Net module? If so, probably not. A VB.Net module[/color]
is[color=blue]
> really just a sealed(NotInher itable) class with static (Shared) members,[/color]
so[color=blue]
> there isn't any particular need for the "module" syntax in C#. For[/color]
example,[color=blue]
> these code snippets are identical:
>
> Module Module1
>
> Sub Main()
> DoSomething()
> End Sub
>
> End Module
>
>
> sealed class Module1 {
>
> static void Main() {
> DoSomething();
> }
>
> }
>
>
> For details:
> "Visual Basic .NET Internals"
>[/color]
http://msdn.microsoft.com/library/de...tinternals.asp[color=blue]
>
>
> "Peter Rilling" <peter@nospam.r illing.net> wrote in message
> news:OsDslzx4DH A.2136@TK2MSFTN GP12.phx.gbl...[color=green]
> > Are there any plans to support C# modules in VS.NET in a future version.
> >
> >[/color]
>
>[/color]
Comment
-
Jay B. Harlow [MVP - Outlook]
Re: modules in VS.NET.
Peter,
I understand that Whidbey (VS.NET 2004) will support .net modules.
See the thread titled "'static library' in .net 2.0?" in the
microsoft.publi c.dotnet.framew ork newsgroup around 20 January 2004.
I understand that VS.NET 2004 should be available late 2004.
Hope this helps
Jay
"Peter Rilling" <peter@nospam.r illing.net> wrote in message
news:OsDslzx4DH A.2136@TK2MSFTN GP12.phx.gbl...[color=blue]
> Are there any plans to support C# modules in VS.NET in a future version.
>
>[/color]
Comment
Comment