If you are a multi language developer, you’ll surely make use of one of these nice tools to convert between different languages.
I’m sure there are alot of programs out there but this web based “Code Translator” one is very fast and on fly convertion. You just paste the code or type the code and it will convert as you type. No need to press enter or whatso ever. If you delete one line, the preview code will remove that line as well. Very cool.

This service will translate the code for you, just start typing the code or upload a file to translate it.
For now it only supports from VB.NET to C# and from C# to VB.NET.
To use it you can either:

1. Start typing your code.
2. Copy and Paste the code in the Code Text Box.
3. Translate an entire file using the file upload.
Link: Code Translator

If you don’t like web based convertor and feel like have it on your system, you gotta try my favorite Lutz Roeder’s .Net Reflector program which can convert to quite a few languages.

Reflector for .NET
Reflector is a class browser for .NET components. It supports assembly and namespace views, type and member search, XML documentation, call and callee graphs, IL, Visual Basic, Delphi and C# decompiler, dependency trees, base type and derived type hierarchies and resource viewers.

You can convert up to 4 languages (IL, C#, VB, Delphi). Another coolest function the “Reflector” provide is the ability to disassemble/decompile various assembly files (.dll and .exe).
Well yah, you can easily steal others compiled codes just by using “Reflector” to decompile it.
It’ll list down all the classes, functions and everything from your assembly file. Sweet hah?

It’s very useful for me cos’ I sometime need to steal reference others codes and make a few convertion between languages, so yah I really love that program.

Our trainer Steve Rodgers is the one who introduced us with both the convertors and their usefulness.
My sincere appreciation goes to him. Thanks.

If you know any other good one like this, do let me know.
Cheers.

Seriously this is just too much pain for me. May be I don’t know the easy steps or there is just no easy way out.

Web projects have always been in conflict with Visual Source Safe in many areas especially when adding to VSS with proper directory mapping and moving projects around different VSS DBs.

I unbind the solution, unbind the project, then bind to new DB. First it seems all right with every files checked in. Then I can’t build nor save the whole project. Something about “check out solution” to build or “discard memory change”. Both option won’t save properly. The next restart of the solution will not include the web project and give you a project not found error.

I remove all .scc, mssccprj.scc and .csproj.vspscc files from solution as well as the project and try again. Still giving

me that same old shit error! This is just freaking hell, taking too much of my time trying many different ways.

Some projects binded well after about 3 tries but some just not happening. I tried 6 times for one project and finally about to give up, found the solution.
It’s not a good solution but it’s working.

First of all you’ll have to get rid of all those, vss associated, mentioned files above. Just search in the project folders and delete all.
Once you’ve done that, open solution file (.sln) and project file (.csproj) in NOTEPAD!
Yah you really need to play around with those source files.

In both files, you’ll see some encrypted codes and some understanding configurations. Now you know what to do.
Just have to delete all VSS config parts. Oh yah, you’ll have to uncheck “Read Only” permission from all your files so better allow read to the whole project folder.

Ok back to solution file, you need to remove “GlobalSection(SourceCodeControl)” bit, similar to the following.


GlobalSection(SourceCodeControl) = preSolution
SccNumberOfProjects = 1
SccLocalPath0 = .
CanCheckoutShared = true
SolutionUniqueID = {04C8BE20-2A9D-4E0B-9E42-AA9E45834A6F}
EndGlobalSection


Again from project (.csproj) file, delete the followings from the very first config tag.


SccProjectName = "SAK"
SccLocalPath = "SAK"
SccAuxPath = "SAK"
SccProvider = "SAK"


Now that should set things right and your project becomes fresh, offline, unbinded version. You can finally proceed to the binding with new VSSDB as normal new project binding steps.

phweeewwwwww!

That’s the only way I can think of to make it work and it took me hell lotta time to figure it out. So here you go – my note of struggling with vss transfer.
Do let me know if you have better/easier solution to this problem as I very much wish to know the proper method rather than scratching head, pulling hairs, banging around, following above steps.

a. Open Microsoft Visual Studio and create new blank solution your project directory. Since I’ve set up D:\may\dev as my projects folder, added new blank solution “VSSDemoSolution” in there.

b. Once you have your solution file, you can add the solution to the source safe by
i. Right click on the solution > add solution to source control or
ii. File > Source Control > Add Solution to Source Control

c. It will ask you to choose your VSS DB and login to it. Once you’ve login “Add to Source Project” dialogue box will pop up with your solution name with .root extension in the project text box. You can either remove the .root from the solution file name and click “Create” to create a folder or simply by removing the whole name and click “OK” will add the solution file to the VSS. My preference is to remove the whole given name from the Project text box and click on “OK” button. Save a few mouse clicks.

d. Once been done, you should be able to see your solution file added to in the VSS Explorer. One irritating thing about source safe is that there is no auto refresh or F5 which make you to either close the explorer and reopen it or collapse the tree view and extend again or just click on refresh button.
Now you have successfully added a new solution to source safe database.

Open the VSS Explorer, it’ll ask you to choose the specific database.

VSS Explorer displays important status information, such as your current working folder, search criteria, number of files, and so on. Some of this information is shown in file pane column headings, and other information is shown in the status bar at the bottom of the VSS Explorer window. The title bar of VSS Explorer shows the database you are connected to. VSS Explorer uses symbols to provide information about the files and projects.

Browse to the location where you create your db and point to srcsafe.ini. (In my example D:\may\DATA\VSSDemo\srcsafe.ini is where my database is and I’ve given the name “VSSDemo” for that database.)

After selecting the required database, you may have to login with your username and password. Since this is my local VSS, I can use “admin” with no password to login to any database.

You will then be able to access the VSS Explorer as shown in the following figure.

By default there is no working folder been set. You will need to set up your working folder according to your directory structure.

The working folder is where you actually work on a file. When you Check Out or Get a file, VSS copies the item into your working folder for that project. After you make changes to the file and check it in, VSS copies it from your working folder back into the database.

Since my projects are going to be in D:\may\dev, I’ve set my root “$” to be D:\may\dev.
NB: While you are working with the team, it is very important that, all your team members set up their local directory the same structure as in VSS. This will make it a lot easier for working with files check-ins/outs.

Currently we are setting up the proper team environment and all necessary procedures to start our main project of the year. We’ve been looking through and studying many to get ready for that including Visual Source Safe which is one of the requirements for team project.

Personally I hate VSS and I prefer not to work with it as much as possible. There are lots of personal reasons for that one of which is I do not like working with team which always mess up my schedules, another is VSS is a big pain to work with. Anyway I can’t complain since we all be using that a lot so I tried to familiarize and learn it as much as I can. I’ll be posting some notes on VSS as I study in coming week. Here is the first lots.

Creating a VSS Database

• From VSS Administrator panel > Tools > Create Databases
• Browse to a directory where you want to place your VSS DB (If you are saving your DB on the server then you need to map the drive before choosing the mapped drive)
• Click on “Ok” and it will create new VSS DB in the specified location.
• More options can be set on your Db by selecting Tools > options
• You may wish to add team members/users of the db by creating new users to your db.
• The VSS Db folder now contains:
  • Data folder
  • Temp folder
  • Users folder
  • srcsafe.ini and
  • users.txt

For the purpose of this demo, I’ll be using D:\ for all my project files.
Good readings from MSDN Library:
ms-help://MS.MSDNQTR.2003FEB.1033/dnbda/html/tdlg_ch6.htm
ms-help://MS.MSDNQTR.2003FEB.1033/guides/html/vstskworking_folders.htm

By default, once you create web applications/services, the project files are saved in Inetpub > wwwroot directory.

To move from default location to your own project directory you must:

1. first, set up the folder in required directory,
2. Create Virtuary Directory using IIS to point to your folder,
3. Using VS.net create new web application with the same virtuary directory name you created in Step 2.

The new project now will be saved in the folder you speficied rather than in default wwwroot folder. This makes it alot easier to manage your project files and better work folder organization.

Welcome to Mayvelous.com. This is my very first post and I hope to start my blogging here.
Please come back again soon for further updates.
Thanks for visiting.

Good evening to you all.
May.