Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / VB.NET / April 2007

Tip: Looking for answers? Try searching our database.

.NET Project Compatability

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
zacks@construction-imaging.com - 19 Apr 2007 15:59 GMT
Using VS2005.

Are .NET projects written with different languages compatable with
each other? In other words, can I reference a VB.NET class library in
a C#.NET application and vice-versa?
Rory Becker - 19 Apr 2007 16:08 GMT
> Using VS2005.
>
> Are .NET projects written with different languages compatable with
> each other? In other words, can I reference a VB.NET class library in
> a C#.NET application and vice-versa?

Yes you can

Compiled projects are not VB or C# they are just (IL) DLLs/Exes

Also you can create solutions which contain both vb.net and c# projects

--
Rory
Duracel - 19 Apr 2007 18:17 GMT
But of course, you can't mix C# and Vb.NET (say) source files in the same
project ;).

> Using VS2005.
>
> Are .NET projects written with different languages compatable with
> each other? In other words, can I reference a VB.NET class library in
> a C#.NET application and vice-versa?
Rory Becker - 19 Apr 2007 18:32 GMT
> But of course, you can't mix C# and Vb.NET (say) source files in the
> same project ;).

Something I would dearly love to be able to do.

--
Rory
zacks@construction-imaging.com - 19 Apr 2007 19:54 GMT
> But of course, you can't mix C# and Vb.NET (say) source files in the same
> project ;).

Yes, I have heard that. Is there a legitimate reason for that?

> <z...@construction-imaging.com> wrote in message
>
[quoted text clipped - 5 lines]
> > each other? In other words, can I reference a VB.NET class library in
> > a C#.NET application and vice-versa?
Rory Becker - 19 Apr 2007 20:29 GMT
>> But of course, you can't mix C# and Vb.NET (say) source files in the
>> same project ;).
>>
> Yes, I have heard that. Is there a legitimate reason for that?

Well there are reasons. How legitimate they are is a matter for debate :)

There vb.net team and the c# team inside microsoft are different sets of
people.

This has 2 major advantages for MS...

1.> Competing teams promote competition and therefore furthering of the product
suite as a whole.

2.> If you didn't have to choose between c# and vb.net, you would have to
find some other holy war to fight over and that (shudder) might have to involve
a non-ms language/practice)

Please note: I really like DotNet, I just really favor multi-language projects.
I'd really like to be able to combine vb.net, c#, c++ and IL in a single
project (and no ILMerge isn't good enough... I want this as an IDE experience)

I think each language has it's place and that each is very good at a particular
set of things. I'd just like to be able to combine the best of each :)

--
Rory
per9000 - 24 Apr 2007 09:45 GMT
<snip>

> Please note: I really like DotNet, I just really favor multi-language projects.
> I'd really like to be able to combine vb.net, c#, c++ and IL in a single
> project (and no ILMerge isn't good enough... I want this as an IDE experience)
>
> I think each language has it's place and that each is very good at a particular
> set of things. I'd just like to be able to combine the best of each :)

<snip>

hear hear

Let's not forget C, Python and perhaps also LaTeX.

In the same IDE... Now isn't that the wet dream of every code-monkey.
[:)]-|--<

/Per

--

Per Erik Strandberg
.NET Architect, et cetera
Tomlab Optimization Inc.
http://tomopt.com/tomnet/
Rory Becker - 24 Apr 2007 11:31 GMT
> <snip>
>
[quoted text clipped - 14 lines]
>
> In the same IDE... Now isn't that the wet dream of every code-monkey.

I sense a little sarcasm (Always hard to tell for certain in the written
word.)

However I would certainly not object to any language being able to integrate
in this fashion.

Of course you would pick and choose which languages you had in your own IDE.

I think it would be great to create an addtional partial class file in order
to implement some functionality in c# when the existing vb.net class didn't
support the functionality you were after.

Whilst this could be seriously abused, I think it could also prove useful.

Writing code in...

Whitespace( http://en.wikipedia.org/wiki/Whitespace_(programming_language) )
Or
BrainFuck (http://en.wikipedia.org/wiki/Brainfuck) (Sorry about the language
:))

... would still be pretty stupid :)

But when something is truely best represented in a different language then
it's a little harsh to make the programmer create an entirely new project
just to support this.

--
Rory
per9000 - 24 Apr 2007 11:41 GMT
<snip>

> I sense a little sarcasm (Always hard to tell for certain in the written
> word.)

Ok, I went a little far with Python and LaTeX, but if I could have a
Visual Studio and/or Open Source alternative (SharpAndNativeDevelop
perhaps) that would allow me to easily integrate native code (f.x: C)
and .NET (f.x. C#) then I'd be really happy.

/Per

PS: I think all editors would have problems with Whitespace due to the
default indentation, but perhaps Emacs has Intellisense for it...
[:)]-|--<

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.