Cathi;

I have commented on the use of more than one language for .NET some time ago. It can also be a problem as far as available manpower is concerned and the abilities of each developer. I have worked in one-person shops as well as six person shops.

Here is one scenario: A corporation hires 5 developers each using a different language for .NET development. As an example an object created in VB.NET is sub classed using C#. A problem requiring debugging or an addition to one or both objects is required. Hopefully you will have personal with the proper skill sets to implement the requirements in a timely fashion. Developers come and go, and may be off work for any number of reasons at any point in time. This can lead to problems as no one will have a skill set to cover all languages .NET allows us to embrace.

At the corporate level or the one-person shop it would seem wise to limit the languages you will use for in house developers and consultants that will work for you. Thus you should establish an in house standard to include which language or languages will be used.

Tom


>One of the greatest features of .NET I think is how you can each be working on the same application and use your language of choice. It's great to hear the success stories.
>
>>Pretty much the reason for me. I had to do most of my part in Winforms. I picked VB over C# because at lease I was acquainted with the syntax. As Mike has said it really has gone well. So far I'm really pleased. I'm sure we will be tracking down a few more gotcha's but they have done all the required stuff with no problems.
>>
>>>Mike;
>>>
>>>Is that why you and Jeff have been "so quiet"? :) Good work and glad to hear that you have released a useful application! We need more messages like yours.
>>>
>>>Tom
>>>
>>>
>>>>After 6 months of development we have finally released our first major .NET based application. Spent all weekend converting from an aging FoxPro 2.6 DOS based system and kicked the new app online Monday morning. So far no major startup problems, just typical minor stuff. Users are still in a “dazed and amazed” state even after a month of testing. I was basically getting beat up to release the system into production by them. What can I say, despite all the naysayers - .NET ROCKS and IS ready for prime time!
>>>>
>>>>Brief system overview:
>>>>Order processing system for repair facility.
>>>>Intranet based using browser front end for data entry. This is not a “dumb” browser client but one designed using a rich DHTML UI. XML data feeds and data islands used for customer and part lookup.
>>>>Win form based monitor handles printing of shippers, labels, etc.
>>>>Web services provide customer lookup, parts data feed, credit card processing - to mention a few.
>>>>Internet based order status inquiry for customers.
>>>>SQL server backend
>>>>EDI data feeds to corporate MRP to handle invoicing, customer and part updates.
>>>>Fox is still alive - reports that required considerable data processing were developed with VFP 7.0.
>>>>
>>>>Major perk - This was our last active DOS based application.
>>>>Major drawback - This was our last active DOS based application. <s>