NT Client

kasti · Post by **kasti** » Tue Jun 29, 2004 7:12 am

Is there any plan/possibility to run Vault client under NT?

sterwill · Post by **sterwill** » Tue Jun 29, 2004 7:40 am

If the .NET Framework 1.1 runs under NT, the Vault client will. According to Microsoft's .NET framework download page (here), the .NET framework will run under Windows NT 4.0 with SP6a.

kasti · Post by **kasti** » Tue Jun 29, 2004 11:46 pm

That is what I thought, so I installed the Framework, but Vault client refuses to install (Windows 2000sp3+ required). Also the Sourcegear website lists 2000 as minimum.

Right now we are evaluating Vault and it would be important for us to run it on NT too since about 20 Developers are still under NT developing for NT target....

Please let me know if there is a way to do this.

Guest · Post by **Guest** » Wed Jun 30, 2004 2:31 am

Did some more testing:

Installed Vault onto XP, copied to NT client. It actually runs!

Only ran into one problem so far: If no working folder is set, you get the error message "Object reference not set to an instance of an object" when you do a get etc.

Once I set this working folder with the command line client, everything works perfectly.

In other words: Guys, you are almost there! I know you dont support NT, but have you got an interest to get it working 100% under NT also?

sterwill · Post by **sterwill** » Wed Jun 30, 2004 7:55 am

I don't think NT support is a top priority (we haven't had many requests), but if the fix for the working folder problem is simple, we may be able to work it into an upcoming release. We're planning to change the way we set working folders in the GUI clients because of the difficulties we've had with the "browse for folder" dialogs on different Windows platforms. On Windows 2000, it works pretty well; on XP there are some quirks (what you type doesn't seem to matter, only what's selected). Does the dialog work at all on NT (do you get the exception before or after browsing for a folder)?

I think the new working folder browser is scheduled to appear in Vault 2.1, which may solve your problem.

As for the installer, it sounds like we (or some code the installer tools automatically run) are checking for 2000 at a minimum, instead of NT 4 SP6a.

kasti · Post by **kasti** » Wed Jun 30, 2004 8:25 am

Actually, most commands fail with this error if no working folder is set.

Some are: checkout, get, set working folder...
Commands that work: view (file)

When the error occurs, client has to then be killed in task manager. If there is any debug files from the client I can send you let me know.

About installer: Is it possible to change the installer requirement to NTsp6a ? Right now I just copied the directory/registry from an XP machine, this could I guess also cause problems.

Thanks for the quick response.

kasti · Post by **kasti** » Wed Jun 30, 2004 8:27 am

Sorry, forgot to answer your question...

Nope, the "set working folder" dialog does not come up at all. Exception comes immediatly.

dan · Post by **dan** » Wed Jun 30, 2004 8:39 am

Another thing that might not work is the file system watcher. If you get up and running, verify whether the status of files are automatically updated (e.g., when you edit a file, does the file status become edited, and if you don't require checkouts, does it get added to the pending change set)? If they don't, it means the file system watcher doesn't work on NT. There wouldn't be much we could do about that if it is the case.

kasti · Post by **kasti** » Wed Jun 30, 2004 8:50 am

Filesystem watcher is working just fine:

checkout, edit -> status edited
modify file without checkout -> status renegade

Come on, lower the spec to NTsp6a

dan · Post by **dan** » Wed Jun 30, 2004 10:46 am

OK - that is good to know. As Shaw said, we were already planning on changing the Set Working Folder dialog in the 2.1 timeframe, so we'll see how far along that gets us.