The language wars - round 3

[Kevin Jackson]

We are starting a .NET ASP.NET project here and we have the VB.NET camp and
the C# camp. I have a few questions.

What problems will we run into if the code behind is in VB.NET and our
ServicedComponents are C#?

Are there any caveats mixing the two languages?

Thanks

 

[Daniel O'Connell [C# MVP]]

We are starting a .NET ASP.NET project here and we have the VB.NET camp
and
the C# camp. I have a few questions.

What problems will we run into if the code behind is in VB.NET and our
ServicedComponents are C#?

Are there any caveats mixing the two languages?

Thanks

As long as you follow CLS guidelines, you shouldn't have any trouble
whatsoever. Basically don't expose any unsafe methods(or do so only for
performance reasons, always provide a safe alternative. I doubt this will be
an issue in ServicedComponents anyway...not sure how the pointer marshalling
would work in this case), don't expose unsigned data types, and don't name
any exposed members with names that differ only by case. Beyond that you
should have no problems with usual constructs.

 

[Sam Gentile [MVP - C#/.NET]]

What problems will we run into if the code behind is in VB.NET and our

ServicedComponents are C#?

Daniel already covered quite well sticking to CLS types, etc. From the
ES/ServicedComponent aspect, there should be no issues as the ES/COM+ of it
is implemented internally and via the CLR and independent of language. As
long as you are calling from other managed languages, like VB.NET, there
should be no problems, at least language wise. Its' when you mix in Interop
that it gets funky-)


--
----------------------------------
Sam Gentile
MVP - C#/.NET
INETA Speaker http://www.ineta.org/DesktopDefault.aspx
Read my blog at http://samgentile.com/blog/

 

[Kevin Jackson]

Thanks for both your replies.

I'm strongly suggesting that these two groups settle their differences and
finalize on one language.

However, most of what will be going on is indeed code-behind calling into
ES/COM+ ServicedComponents. So it sounds like if we go with two languages,
it will work.

Kevin

 

[Sam Gentile [MVP - C#/.NET]]

I'm strongly suggesting that these two groups settle their differences and
finalize on one language

This is straying off topic but that's what the CTS, CLR and BCL already do
(http://samgentile.com/blog/articles/1989.aspx). 90% of what people "think"
is C# or VB.NET is actually BCL calls like System.Console.WriteLine and
expressing the semantics of the CLR. The language issue is merely a
syntactical preference pretty much except for a few issues of difference.
It's said that the languages will now start to diverge to better serve their
user base in the future,

--
----------------------------------
Sam Gentile
MVP - C#/.NET
INETA Speaker http://www.ineta.org/DesktopDefault.aspx
Read my blog at http://samgentile.com/blog/

 

[Jeffrey Tan[MSFT]]

Hi Kevin,

Does Sam's reply make sense to you? Do you still have any concern on this
issue?

Please feel free to post. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.