Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Visual Basic > VB.NET 1.0 > VB.NET 2002/2003 Basics
Password Reminder
Register
| FAQ | Members List | Search | Today's Posts | Mark Forums Read
VB.NET 2002/2003 Basics For coders who are new to Visual Basic, working in .NET versions 2002 or 2003 (1.0 and 1.1).
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VB.NET 2002/2003 Basics section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #11 (permalink)  
Old August 17th, 2004, 10:43 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Although Hal makes a very compelling point regarding standardization, there is no reason you can't build this kind of system with different projects (and possibly projects of different languages). If you follow the methods I have described and properly build classes with methods (or properties) that accept the datatypes that you need to hand around, you can work quite comfortably with multi-project/language systems. (This still doesn' help your situation with app to app data handling.)

My development team has standardized on VB.NET for UI projects because of VB.NET's friendliness with the VS.NET IDE for UI design and C# for the other tiers because of C#'s native documentation features.
Reply With Quote
  #12 (permalink)  
Old August 17th, 2004, 01:35 PM
Friend of Wrox
 
Join Date: Jun 2003
Location: , , .
Posts: 540
Thanks: 0
Thanked 4 Times in 4 Posts
Default

I would agree assuming that you have numerous developers familiar with each language you use. If you know both C# and VB.Net, then it isn't going to kill you if you lose your only other C# developer.

However, if all you know is C# and you lose your developer that knows both (or just VB), then you have a completely different situation to deal with.

What if one of the classes that you use regularly was developed in the other language and suddenly it is causing errors? Just something think about.

J
Reply With Quote
  #13 (permalink)  
Old August 17th, 2004, 08:49 PM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Remember that VB.NET and C# are .NET compliant languages. Aside from a very few differences between what each language can do, there is little reason that I or the other developers can switch between the languages. We are writing .NET code using .NET classes which is the same regardless of the language syntax. Switching between those languages (for me at least) is pretty simple because it's just a simple change of syntax. Frankly I don't want to work with, nor would I hire a programmer who can't figure out how to write in either language in the .NET environment. If they know the .NET framework well enough to perform their tasks sufficiently, then I'm happy. Seeing as most people learn (real) programming in C or C++, they will be capable of figuring out .NET regardless of the language. That's the beauty of the CLR.
Reply With Quote
  #14 (permalink)  
Old August 17th, 2004, 11:51 PM
Friend of Wrox
 
Join Date: Jun 2003
Location: , , .
Posts: 540
Thanks: 0
Thanked 4 Times in 4 Posts
Default

My apologies if VB is not a "real" language but that is the background that I come from. I have never coded in C#, or C for that matter. Sure I have looked at examples and, for the most part, understood it. There were enough syntax differences, though, that I wouldn't be comfortable suddenly being thrust into it if an emergency came up and it needed to be resolved immediately. There would still be some learning curve that I would have.

Could I learn it? Yes. Have I had time? No. So if my manager came to me tomorrow and said "I need this error resolved within the next couple of hours." and it was written in C#, I would be without a paddle. I would love to spend all day learning new languages, but unfortunately in my position I don't have that luxury.
Reply With Quote
  #15 (permalink)  
Old August 18th, 2004, 07:57 AM
Authorized User
 
Join Date: Mar 2004
Location: Maumee, OH, USA.
Posts: 61
Thanks: 0
Thanked 0 Times in 0 Posts
Default

One of the things .NET touted was the interoperability between languages since it all goes to IL. You would think that what I originally proposed would be a lot simpler to accomplish. Any more ideas on how this might be accomplished?
Reply With Quote
  #16 (permalink)  
Old August 18th, 2004, 08:25 AM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,102
Thanks: 0
Thanked 2 Times in 2 Posts
Default

Peter- Let me say I agree, there is no reason you CAN'T build different projects and use different languages- I just think a good shop has some standards- even in that standard is to split the languages as you have done at your shop. I do, however, consider myself a real programmer- and I have never worked with C or C++. None of my jobs ever "needed" me to know how to use those languages, as a result I never learned them. I am 100% self-taught as a developer. Books and so forth. No training in development at all, really.

J- I understand what your saying- That's why I think a standard is good and you make sure people you hire can meet that standard. Without a standard - who do you hire?

BSkelding (you have a first name?)- Yes, you have interoperability between languages. Each project (and I mean VS.NET project), however, must be in one language. Each Project will compile into one or more assemblies. Namespaces can cross Assemblies. The "Issue" is that in order to reference an assembly (and have a job compile) you need to have the assemblies that there is a dependency on compiled first. So if one person is creating the UI to talk to Business objects- then the business objects need to exist first. The flaw in yor design is your not seperating the business work from the UI work. Doing them in the same project, and expecting them to cross over assembly's (which might not exist) won't work. If you create Project 1.. compile that.. and then create a reference to project 1 in project 2- you can use the functionality from Project 1 in Project 2. No "passing" is required. Just use it like any other object. It seems your missing knowledge on some of the fundamental parts of the framework- and I suggest you get a book and read it, because I dont't think any of us want to re-write a book here in the forums. The forums are to help people with specific problems, not provide .NET training.

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Help passing login info to new page peterh Classic ASP Basics 4 January 10th, 2008 12:39 PM
HELP:Join & Split Projects/soln Aritra ASP.NET 1.0 and 1.1 Basics 4 March 2nd, 2007 03:04 AM
Passing Database Logon Info happyslug BOOK: Professional Crystal Reports for VS.NET 1 February 14th, 2005 08:48 AM
Passing logon info sandeep Crystal Reports 1 October 6th, 2004 08:41 AM



All times are GMT -4. The time now is 12:45 PM.


Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.