Why Shlok
Migration VB6 to VB.Net Migration VSS to TFS
Recent Case Studies
Quality

Our strategic presence in both Europe and India make possible a development model that is highly productive and accurate. With quality people and an infrastructure already in place SHLOK has been delivering acclaimed products to their clients on time.  More...

Every Business is Unique ,Every Client is Unique, Every Solution is Unique SHLOK with a perfect blend of the Business and Technical Expertise provides end to end Complete IT Solutions, be it a product design, a simple website, a technology solution to an existing business problem or a maintenance and support plan  More...

We convert to technology products the deep rooted and in-depth domain expertise of our Clients and Partners. With our cost effective R & D Activities at our offshore centers in India, SHLOK will be your apt partner to deliver Production Design and Development services. More...

SHLOK takes up maintenance and support of Applications delivered by SHLOK or already existing applications at the client  More...

SHLOK solutions enhance the bottom lines of customers by eliminating process inefficiencies, improving supplier collaboration, and elevating overall service. Read our case studies to see how some of our customers are achieving return values of their investments from SHLOK solutions More...


Subscribe here for our newsletter Be the first to hear about new products, discounts, and more with our roughly twice-a-month newsletter.

Migration Service

SHLOK with its Strong Reputaion in Microsoft Technologies in recent time has extended its services in Migrating/Converting the VB6 Application to .NET applications.

Why Should I Migrate?

Visual Basic 6.0 (VB 6.0) is already quiet obselete and it no longer supported by Microsoft
ref support.microsoft.com
May be in around 5 years from now VB would have a status that COBOL/PASCAL have today.
Integration with the latest technology is becoming impossible
Error handling efficiency in VB6 is becoming tedious as single threading is the only possibility
Code access security is less in VB6

What is the Solution?

Rewrite
Replace
Reuse
Migrate

Is it high time do ?

There is no real urgency to migrate
But we all know your software would take a lot of planning and effort to migrate
5 years from now,it will be more expensive and more difficult to migrate
In the time we are still with VB 6.0 we arent able take advantage of new technologies

Is this is an automated or manual process?

On a rough scale, migration is 50-80% automated , the rest of the process is manual

VB.net or ASP.net or Others & Why ?

VB6 to VB.net is Recommonded

VB.Net Re-use% = 80.
But we all know your software would take a lot of planning and effort to migrate
Other technologies like Java,Outsystems Re-use% = almost 0. We might have to re-do everything from scratch,
which will be very expensive effort intensive and time consuming
The existing team can be easily trained in VB.Net and they can quick start working in VB.Net , migrating and developing

What is the Methodology used?

Migrate by Components
Migrate by Projects
Migrate by Concepts

Dose this affects my capital investment?

No, It does not affect your capital Investment.