[3.5.2] Problem with check-in (transaction aborted)

[plykkegaard]

Hi

We are running with a fairly old vault system - 3.5.2 (5087) using is as a repository for Biztalk projects as well as various .NET projects/solutions
I have discovered a few issues along the way, just wondering whether this has been fix in later versions

Through the standalone client I have problems checking in speciel biztalk project files
Eg
Flow_DINS.odx.cs (codebehind C# sourcefil
Vault fails with a transaction aborted
The solution is to set a specific type before you do a check-out (type = use default | mergeable | binary)
In the above case mergeable is working fine

I have also another challenge with some old sourcefiles carrying ascii 164 ("sun" - Alt Gr-4) which Vault seems to dislike, the character is stripped from sourcefile at check-in

Suggestion other than upgrade immediately are also highly appreciated

Thanks /Peter

[plykkegaard]

Hi

Wondering if the "... make sure the file extensions are listed in the mergeable file types in the repository options in the Admin web page" could solve the problem with "*.odx.cs" files?

Thanks /Peter

[Beth]

Wondering if the "... make sure the file extensions are listed in the mergeable file types in the repository options in the Admin web page" could solve the problem with "*.odx.cs" files?

I think .cs files should be listed already, but it can't hurt to add .odx.cs unless it's not a text file.

On the problem with the old source files in ascii 164, could you zip up and email me one of those files so I could take a closer look? You can send that to support at sourcegear.com (attn: Beth). Could you include a link to this forum thread?

[plykkegaard]

I think .cs files should be listed already, but it can't hurt to add .odx.cs unless it's not a text file.?

cs files (eg myclass.cs) is working without hickups
The *.odx.cs files are indeed "plain" C# sourcefile - like eg *.aspx.cs - I don't have problems with the latter

On the problem with the old source files in ascii 164, could you zip up and email me one of those files so I could take a closer look? You can send that to support at sourcegear.com (attn: Beth). Could you include a link to this forum thread?

I will see if I can fix the problem by adding the file as an mergeable/text file - I used binary when I experienced the problem
And yes - I'll send you a copy, maybe just a dummy file having the problem in question

rgds /Peter

[Beth]

Since I haven't heard anything more, I'm going to assume you are working ok right now.