-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RiskClassifier.sln not building with release.bat on Win 8.1 with VS 2013 sdk etc... #18
Comments
Update... seems to be a problem with the references for..... Microsoft.VisualStudio.* ....there because there is a lot of this kind of CTE complaint in VS 2013.... Error 85 The type or namespace name 'Text' does not exist in the namespace 'Microsoft.VisualStudio' (are you missing an assembly reference?) C:\GitHub01\ContinuousTests\src\AutoTest.VS.RiskClassifier\RiskClassifier\CodeModelCache.cs 239 90 AutoTest.VS.RiskClassifier ....and so I double-checked that the SDK was installed (it is), and I tried removing and re-adding the references (no luck).... ....and so this is still broken.... |
Hi Mark, Sorry I was a bit late with merging a few pull requests. One of them lists -Svein Arne On Wed, Sep 30, 2015 at 9:06 PM Mark Kamoski [email protected]
|
acken -- Ok, great, that helped. I did see these links online. But I have not yet tried any of the suggestions at those links. My current questions are as follows. Do I need to have VS 2010 installed in order to get ContinuousTests to install? And if Yes, then will VS 2010 Express suffice? Is VS 2013 supported at all for Continuous tests? Generally, do you (or does anyone) know of a way to fix this or workaround it? Please advise. Thanks. -- Mark Kamoski |
It should try to instal under Visual Studio 2013 but I have not tested that On Thu, Oct 1, 2015 at 3:45 PM Mark Kamoski [email protected]
|
Resharper installed by chance? On Thu, Oct 1, 2015 at 3:57 PM, Mark Kamoski [email protected]
Studying for the Turing test |
gregoryyoung (and all) -- http://blog.jessehouwing.nl/2013/12/enabling-mighty-moose-for-visual-studio.html And, as far as I can tell, the thing is working. |
So normally when you get a hang like that something installed into VS On Thu, Oct 1, 2015 at 4:11 PM, Mark Kamoski [email protected]
Studying for the Turing test |
Dear ContinuousTest Power Users --
Please help.
I am new here and I am getting a build failure running "release.bat" on Win 8.1 with VS 2013 sdk, etc.
I wanted to attach the DOS output stream, but oddly, GitHub is not letting me attach a 274kb plain text file, so some snippets are below.
BTW I searched for "*.sln" in the ContinuousTests hive and I am trying to build them one-b-one manually in VS 2013 Pro on Win 8.1 but there are TON of sln files so I could use some help.
The following seem to be issues...
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 09/30/2015 13:18:37.
Project "c:\GitHub01\ContinuousTests\src\AutoTest.VS.RiskClassifier\RiskClassifier.sln" on node 1 (rebuild target(s)).
ValidateSolutionConfiguration:
Building solution configuration "Release|Any CPU".
Project "c:\GitHub01\ContinuousTests\src\AutoTest.VS.RiskClassifier\RiskClassifier.sln" (1) is building "c:\GitHub01\Continuous
Tests\src\AutoTest.VS.RiskClassifier\RiskClassifier\AutoTest.VS.RiskClassifier.csproj" (2) on node 1 (Rebuild target(s)).
c:\GitHub01\ContinuousTests\src\AutoTest.VS.RiskClassifier\RiskClassifier\AutoTest.VS.RiskClassifier.csproj(157,3): error MSB40
19: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\VSSDK\Microsoft.VsSDK.targets" was not fo
und. Confirm that the path in the declaration is correct, and that the file exists on disk.
Done Building Project "c:\GitHub01\ContinuousTests\src\AutoTest.VS.RiskClassifier\RiskClassifier\AutoTest.VS.RiskClassifier.csp
roj" (Rebuild target(s)) -- FAILED.
...etc....
...basically RiskClassifier is hosed....
....will try to hack a workaround but could use help too...
...thanks.
-- Mark Kamoski
The text was updated successfully, but these errors were encountered: