$(QTDIR) is hard coded in vs-addin 1.1.6 for msvc-2010

vs-addin 1.1.6 will create a file for msvc-2010 named Qt4VSPropertySheet.props as a project property file which will be imported by my Qt project. In that file, $(QTDIR) is specified as follows:
<PropertyGroup Label="UserMacros">
<QTDIR>D:\qt</QTDIR>
</PropertyGroup>

this mechnism will make Team Development become very difficult.
Suppose we have two machines A and B, in machine A, we install qt to d:\qt and we set $(QTDIR) to d:\qt; in machine B we install qt to d:\4.7.0 and set $(QTDIR) to d:\qt-4.7.0. the programmer in machine A create a Qt project and add this project to source control system(such as SVN), the *.props file will also be added to source control system because the *.vcxproj file need it. Now the programmer in machine B grab the project from source control system, but the $(QTDIR) stored in *.props is d:\qt, and the the programmer in machine B will encounter the following problems:
1) if he build this project by command line without open it by visual studio 2010, the build will fail because the $(QTDIR) is d:\qt (read from the *.props file) even though he has set $(QTDIR) environment variable to d:\qt-4.7.0
2) if he open this project by visual studio 2010, it seems that visual studio 2010 will change $(QTDIR) to the correct value d:\4.7.0 at the cost that the *.props has to be changed. You know this is unacceptable in team development.

I think this is a regression.