Hello,

I discovered this forum and I have few questions for you.

I'm an IT developer so I develop with many languages (Microsoft Dynamics Nav : C/AL, SLX : VB, SSIS, Reporting, .NET etc...) and my manager give me a new project to do. I have to synchronize our SLX application (6.2.2) with Team Fundation Server. TFS is a source controler which allows you to work locally and then to archive without erasing the work of others team members.

To achieve this, I just have to get the source code however I believe it is stored in the database isn't it? And TFS supports only files with 'text' (regardless of their extension until you can open)

So I want to ask you to know if someone has already implemented a solution between SLX and TFS. Where can I find the SLX source code ?

TFS works with Visual Studio 2010 so if I find the files with VB scripts I could (maybe) develop without Architect because Visual Studio knows the VisualBasic language. Ok, maybe it will be less suitable than Architect...

In my company we want TFS to manage all our source code.

Thanks for your help.

Best regards.

visual studio and vbscript and visualbasic are different animals.....

Excuse me I just started to work with SLX three weeks ago so there is a lot of things I don't know yet.

I thought VBScript and VisualBasic are the same sorry. So with SLX it's VB Script okay.

There's really no good/easy solution to this. That was always a huge flaw with legacy SLX. It just doesn't work with source control at all. New web-based versions of SLX work great with source control systems, but the LAN client does not. There's not going to be a happy end to your search.

The only way to really make use of source control with SLX is to develop using .NET Extensions. Then your source code lives outside of the SLX database and you can put it easily under source control. However, this won't solve any problems with code already in SLX, including all the out of the box code and things already developed and customized. You can choose to develop new things in SLX as .NET Extensions, but for existing stuff you'll be out of luck.