Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SPOCLIENT not set?

131 views
Skip to first unread message

Tim G.

unread,
Mar 18, 2010, 6:47:01 AM3/18/10
to
Hello,

I am trying to open one of the several managed projects within the porting
kit. For instance the DPWS-Stack:
C:\MicroFrameworkPK_v4_0\Framework\Core\Dpws\DpwsStack\Dpws.csproj

I am using Visual Studio 2008 but when trying to open the project I get the
following error message:

"
Unable to read the project file 'Dpws.csproj'.
C:\MicroFrameworkPK_v4_0\Framework\Core\Dpws\DpwsStack.Dpws.csproj(12,11):
The imported project
"C:\tools\Targets\Microsoft.SPOT.CSharp.Targets" was not found.
Confirm ....
"

Now taking a closer look at the second path and the Dpws.csproj at (12,11)
it seems like the $(SPOCLIENT)-makro does not work or the SPOCLIENT-Variable
is not set. Therefore the path is "C:\tools\...." instead of
"C:\MicroFrameworkPK_v4_0\tools\..."

I have already tried to run "setenv_vs9.cmd" which should set SPOCLIENT (via
"setenv_base.cmd" - leading to the same error.
I have also tried to manually set the envirionment variable directly in the
windows registry (adding it to the env-vars of the current user) - again
without success.

Of course I can just create a new project and add all the source-files,
however this is somewhat inconvenient.

Has anyone encountered the same problems?
And more interesting: any suggestions on how to solve this problem?


Thanks in advance.

Regards,

Tim


p.s.: Btw. I am using Windows 7, but a coworker has encoutered the same
problem on WinXP.


Lorenzo Tessiore

unread,
Mar 22, 2010, 11:41:02 AM3/22/10
to
Hello Tim,

after calling setenv_vs9.cmd, you should start VS from within the command
shell where you called setenv_vs9.cmd. Use 'devenv <xxx.csproj'

Regards
Lorenzo

Tim G.

unread,
Mar 23, 2010, 7:36:03 AM3/23/10
to
Hello,

"Lorenzo Tessiore" wrote:

> after calling setenv_vs9.cmd, you should start VS from within the command
> shell where you called setenv_vs9.cmd. Use 'devenv <xxx.csproj'
>

... works perfect. Thanks a lot!


Kudos for the great support around here in the NG - I appreciate it.


Regards, Tim


0 new messages