Doubt to go .Net technology

  • Thread starter Thread starter Igbal
  • Start date Start date
I

Igbal

Hi,

There is doubt to proceed.

There is a product here in VB 6.0 and SQL server.
It's 3 tier architecture.

1. Front end.
2. Business Logic.
3. Back end.

There are 3 options to do on this product:

1. LAN. (Front end and business logic r in the local machines)
2. WAN (Front end in the client machine and business logic and Database in
the server machine)
3. Web (Browser and all others in the server machine)

In the above 3 options, For to convert to .Net environment, Is it
easy(advisable) to do in terms of development and execution time?

Consider the following before answer:

1. Execution time compared with VB 6.0 application.
2. Developement time for migrating.
3. Use the business logic as it is (COM) or new (Assembly)
4. VB (Client server) to ASP.Net (Web application)
5. Future technology.
6. System Configuration.

Suggest me as soon as possible.

Thanks in advance.
 
In general,
1. Execution time compared with VB 6.0 application.

Execution time? A well written VB.NET application can outperform VB6 in
a business service scenario.
2. Developement time for migrating.

With VS.NET 2003, you should see productivity up to 5 times better
(sometimes more, sometimes not that much) than with VB6/ASP3.
3. Use the business logic as it is (COM) or new (Assembly)

You can leave it as COM to start off (use Interop), and migrate as
necesary.
4. VB (Client server) to ASP.Net (Web application)

Depends on your design, features, etc. ASP.NET is where you'll a HUGE
improvement over ASP3.
5. Future technology.

Microsoft is moving most everything to .NET. To take advantage of
future technologies, you'll need .NET.
6. System Configuration.

Depends on the application requirements. The .NET Framework will
install on Win98 and up. ASP.NET will run on Windows 2000 and up.

-mike
MVP
 
From: E.S.Mohammed Igbal

There is confusing situation to convert existing VB application and SQL
Server application to .Net.

1. Tell me why I want to move to .Net? (Advantages)
2. There are 3 requirements for me.
i. LAN - For this, I can convert it into VB to VB.Net.
As I told earlier, It adhers 3 tier architecture.
Front-End, Business Logic and Database.
Here I don't want to migrate Business Logic. Only Front-End. Which
one is best?
i. Migrate entirely (Both Front-End and Business Logic).
ii. Only Front-End.
ii. WAN - For this, There are two ways, I planned.
i. Don't migrate. Put database and business logic dlls in
server machine. Call business logic dlls via HTTP protocol. How to
acheive this?
ii. Convert business login dll in Webservice and call it from
front-end (VB.Net).
iii. Web - It's better to go for ASP.Net.


Please suggest me what I thought is right?

Thanks in advance.

Regards,
E.S.Mohammed Igbal M.Sc.
 
Back
Top