Bug/Request - assembly names

Jared Sullivan · Post by **Jared Sullivan** » Wed Dec 06, 2006 7:02 pm

Hi,

I would like to change project assembly name to "MyProject¹". But VS throws several errors with SOS plugin.

Could this issue please be added to todo list.

Thanks
Jared

lbauer · Post by **lbauer** » Thu Dec 07, 2006 8:57 am

What version of SOS and Visual Studio are you using?

Jared Sullivan · Post by **Jared Sullivan** » Thu Dec 07, 2006 12:44 pm

VS2005(SP1 beta) + SOSClient 4.2 (latest)

NOTE VS VSS Plugin handles such characters as super script as part of the assembly name.

lbauer · Post by **lbauer** » Thu Dec 07, 2006 5:55 pm

Do you get the errors renaming the assembly? Try renaming the assembly in the VSS GUI Client or in Visual Studio.

Or are there errors when doing operations with superscript on the assembly name?

Jared Sullivan · Post by **Jared Sullivan** » Thu Dec 07, 2006 6:57 pm

Yes, I get the error when renamming assembly with SOS Client.

VSS Explorer and VSS Plugin work as expected.

Just to be clear here is steps to reproduce.

1. Right click SS project in VS2005 using SOS plugin
2. Change Assembly name to Something¹

Thats it, I would give you screen dump of error in mail, but not on SOS terminal right now. Messagebox comes up with error int cpp file at line ..

Thanks
Jared

lbauer · Post by **lbauer** » Mon Dec 11, 2006 9:06 am

I couldn't reproduce this. I added a C# Class Library to source control, then right clicked on the name ClassLibrary1 in Solution Explorer and pasted in Something¹. Visual Studio prompted for checkout. I also tried changing the name in the project properties->Assembly Name. That worked, to.

What version of VSS automation component is the SOS Server using?
Here's how to find out:
http://support.sourcegear.com/viewtopic.php?t=1510

Jared Sullivan · Post by **Jared Sullivan** » Mon Dec 11, 2006 1:54 pm

Hi, and thanks for spending time to reproduce, I will reproduce this bug for you and email you some screen shots..very interesting errors.

Jared Sullivan · Post by **Jared Sullivan** » Mon Dec 11, 2006 1:55 pm

I use VB.NET 2005 SP1 beta

lbauer · Post by **lbauer** » Mon Dec 11, 2006 2:42 pm

I use VB.NET 2005 SP1 beta

Sorry I wasn't more clear. I need to know the version of the VSS (Visual SourceSafe) automation component. This is the ssapi.dll provided by the VSS client on the SOS Server machine.

SourceOffSite Server communicates with the VSS database via this automation component, thus the version greatly affects SOS behavior.

This KB article provides instructions on how to determine which version of the ssapi.dll SourceOffSite Server is using:
http://support.sourcegear.com/viewtopic.php?t=1510

Jared Sullivan · Post by **Jared Sullivan** » Mon Dec 11, 2006 10:09 pm

ssapi.dll is 8.0.50727.42 on my Vista SS Server box.

Here is the *exact* step needed to reproduce bug..

1. Create new Project
2. Add project to SS
3. Change project name to WindowsApplication1¹
4. Checkin in and stuff (think errors here first)
5. Then change assembly name to WindowsApplication1¹

Please see my screen shots attached. Sorry I was not as detailed in repo step in first post as I didn't realize it was so quirky to reproduce.

PS. The order of the errors attached is "Your.." , "Some..", "Unexpected.."

Thanks
Jared

lbauer · Post by **lbauer** » Tue Dec 12, 2006 5:12 pm

One of our developers is looking into this and will also try to reproduce it.

We haven't tested SOS on Vista, so we don't know if that's a factor or not.

lbauer · Post by **lbauer** » Wed Jan 03, 2007 11:40 am

Sorry, still can't reproduce this. WindowsApplication1¹ worked fine for the project and assembly name. It's possible that Vista is a factor.

We haven't tested SOS on Vista.

SourceGear Support

Bug/Request - assembly names

Bug/Request - assembly names

Assembly name error

Bug

bug

Full details of bug