Friday, March 19, 2010

Visual Studio Project Converter

Change to vspc folder:
Run command: vspc ["from version" "to version" "fileName" [/option --longOption]] 
e.g: vspc VS2008 VS2005 D:\MyPrj\TestPrj.sln /b /r
=> Convert "TestPrj" solution and "TestPrj" project files from VS2008 downto VS2005 with backup and importing references options.
More details:
Visual Studio .NET solutions converter v.0.9.3
Totally Free(tf:-) by Stoyan Damov. Modified by Nikolay Samofatov

Usage: vspc ["from version" "to version" "fileName" [/option --longOption]]
and : One of the following - VS2002, VS2003, VS2005 or VS2008.

Note that conversion of .NET projects for version 2005 and 2008 is currently not supported. Native C++ projects should convert just fine between any of the above versions.

: The full solution/project file path (all projects in the solution are converted automatically, and I don't think you'll want a separate option on the command line to avoid that:)


/q, --quiet Do not display anything on the console

/b, --backup Backup each converted file


/h, --hintpaths The framework version of the project references (in HintPath) is converted to the default one for the VS project (i.e. 2002 gets version v1.0.3705, 2003 gets v1.1.4322)

/w, --webprojects Convert the web applications projects, found in the solution file;


/p, --relativepaths Fix the "RelativePath" attribute to prepend ".\"

/r, --references Import references, i.e. convert , added by "Add Reference" to include the appropriate .DLLs in stdafx.h, i.e. "#using "... (if the option is missing, you'll be able to open the project, but will have to add the #using clauses by hand)

/c, --nochkclr Remove the "nochkclr.obj" dependency in the linker settings from 2002 projects, add it to 2003 projects (use the option or your project won't compile, unless you have that file)


Visual C++ 2002 (DUH!) DOES NOT support ".resx" files, and refuses to load projects with such files, so I remove them from the project files

Thursday, March 18, 2010

ParaSoft C++Test: Precompile failed

Process exited with code -1073741515

C++Test cannot see cl.exe (with Visual Studio), gcc (with Linux) and its dependencies.

How to fix:
-------- + Make sure that PATH environment is set. We can test the PATH by cmd.exe or shell (env command). Run cl.exe --version to check the path and its dependencies.
-------- + Maybe add $(INSTALL_DIR)\Microsoft Visual Studio 8\Common7\IDE if mspdb80.dll was not found by cl.exe.

Tags: -1073741515, 1073741515, C++Test, parasoft, Precompile, Error, error result, cl.exe, error code, exit code, from cl, visual studio

mspdb80.dll was not found

Set PATH environment: add more $(INSTALL_DIR)\Microsoft Visual Studio 8\Common7\IDE.
e.g: I searched and saw mspdb80.dll in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE

Wednesday, March 17, 2010

disable the M$ C4996

In VS 2005 EE, do:

Project | Properties | Configuration properties | C/C++ | Advanced | Disable specific warning | add the value 4996.



in *.c, *.cpp

Have fun.

iPhone in Vietnam

What a smartphone!

Viettel > Vinaphone == Mobifone ?

Can I do the programing with this Apple phone?

Multi-Targeting: Vs2008 vs Vs2005

One of the big changes that VS 2008 release to support is "Multi-Targeting" - which means that Visual Studio will now support targeting multiple versions of the .NET Framework, and developers will be able to start taking advantage of the new features Visual Studio provides without having to always upgrade their existing projects and deployed applications to use a new version of the .NET Framework library.

One question is: "How to convert VS2005 to VS2008 and vice versa?" - downgrade/upgrade

get site feeds

Can I get site feeds for specific labels?Print Yes, you can! If a blog you read is using labels and also has site feeds enabled, then you can pick and choose which topics you want to subscribe to. The format for label feeds is this:

Be sure to substitute in the correct blog address for blogname and the label you're interested in for labelname. Also, don't miss the hyphen ("-") in the URL. That's not a typo!

Note that a URL of this form will only work if the blog in question is using this specific label, and has also enabled site feeds. However, no special site feed settings are necessary. As long as the basic site feed for posts is enabled (with either short or full descriptions) then label feeds will also work.

Tuesday, March 16, 2010

ParaSoft C++Test: How to test

  1. Open file(s) | Open.
  2. Read Symbols: to pre-compile (PreCompiling, Preparing harness dir, Collecting lib, Collecting symbol definitions, Matching symbol definitions, Creating test driver, Done)
  3. Tests | Test Using | Configurations | Build-in | CodingStandard | Choose CRules, MustHaveRules, NiceToHaveRules, SecurityRules, ShouldHaveRules, ShouldHaveRulesWithPortability. See Coding Standards tab and output window to get information.

ParaSoft C++Test: Test Menu


# Read Symbols: Prompts C++test to parse the selected file, then represent its symbols in the Symbol tree.


# Build Test: Tells C++test to parse the selected file, read its symbols, instrument it (if necessary), then compile and link it.

# Re-read Symbols: Prompts C++test to re-parse the selected file, then refresh its symbols in the Symbol tree. This option is useful if you have changed/updated any of the source code in a file since the last test, or when there are changes in the static or dynamic libraries that are used by the project under test.

# Rebuild Test: Tells C++test to re-parse the selected file, read its symbols, instrument it (if necessary), then compile and link it. This option is useful if you have changed or updated any of the test parameters since the last test.

# Test Using: Tells C++test what Test Configuration (a predefined test scenario) you want it to run for the current test. Test Configurations are described in Selecting and Customizing Test Configurations.

# Test Configurations: Opens the Test Configurations panel, which allows you to add and modify Test Configurations. Test Configurations are described in Selecting and Customizing Test Configurations.

# Import Results: Imports coding standards analysis results from a command-line test into the C++test GUI. See Importing Command-Line Coding Standards Analysis Results to the GUI for details.

# Stop: Stops a test once it has begun. Can also stop the Read Symbols and Build Test actions.

  • Precompiling error with code -1...515: Make sure the PATH environment of compiler is correct. The C++Test cannot search the compiler sothat it cannot build source code. account

Account: vav