Skip to content
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

Open
mkamoski opened this issue Sep 30, 2015 · 8 comments

Comments

@mkamoski
Copy link

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

@mkamoski
Copy link
Author

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....

@acken
Copy link
Member

acken commented Sep 30, 2015

Hi Mark,

Sorry I was a bit late with merging a few pull requests. One of them lists
the 2010 SDK as one of the prerequisites for now.

-Svein Arne

On Wed, Sep 30, 2015 at 9:06 PM Mark Kamoski [email protected]
wrote:

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....


Reply to this email directly or view it on GitHub
#18 (comment)
.

@mkamoski
Copy link
Author

mkamoski commented Oct 1, 2015

acken --

Ok, great, that helped.
I had installed VS 2013 SDK and "release.bat" was failing.
So I just now installed VS 2010 and "release.bat" finishes without error.
I ran the output file.
...\ReleaseBinaries\Installer\ContinuousTests-v1.0.48.exe
But when I did that I got the following error message popup from VS 2010 Shell.
"Invalid license data. Reinstall is required."
(See attachment.)
And then I clicked "Close" in that popup.
And then the "Setup - ContinuousTests" dialog was just frozen on "Resetting addin" and dead.
So I closed that dialog by force.
I then launched VS 2013 and the ContinuousTests addin was not there, as far as I could tell.
So I should say at this point that I do have VS 2013 Pro installed.
But I do NOT have VS 2010 installed at all, not even VS 2010 Express.

I did see these links online.

https://social.msdn.microsoft.com/Forums/en-US/9ff4bb25-eb12-4554-bea1-d67683ab535d/message-visual-studio-2010-shell-invalid-license-data-reinstall-is-required-when-opening-a-vs2010?forum=vssetup

http://stackoverflow.com/questions/2673275/how-do-i-fix-an-invalid-license-data-reinstall-is-required-error-in-visual-c

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

continuoustests invalid license data issue 2015-10-01-09-20

@acken
Copy link
Member

acken commented Oct 1, 2015

It should try to instal under Visual Studio 2013 but I have not tested that
myself as I have not been on VS for a while. I remember someone hacking a
solution for it. I think it was this one
http://blog.jessehouwing.nl/2013/12/enabling-mighty-moose-for-visual-studio.html

On Thu, Oct 1, 2015 at 3:45 PM Mark Kamoski [email protected]
wrote:

acken --

Ok, great, that helped.
I had installed VS 2013 SDK and "release.bat" was failing.
So I just now installed VS 2010 and "release.bat" finishes without error.
I ran the output file.
...\ReleaseBinaries\Installer\ContinuousTests-v1.0.48.exe
But when I did that I got the following error message popup from VS 2010
Shell.
"Invalid license data. Reinstall is required."
(See attachment.)
And then I clicked "Close" in that popup.
And then the "Setup - ContinuousTests" dialog was just frozen on
"Resetting addin" and dead.
So I closed that dialog by force.
I then launched VS 2013 and the ContinuousTests addin was not there, as
far as I could tell.
So I should say at this point that I do have VS 2013 Pro installed.
But I do NOT have VS 2010 installed at all, not even VS 2010 Express.

I did see these links online.

https://social.msdn.microsoft.com/Forums/en-US/9ff4bb25-eb12-4554-bea1-d67683ab535d/message-visual-studio-2010-shell-invalid-license-data-reinstall-is-required-when-opening-a-vs2010?forum=vssetup

http://stackoverflow.com/questions/2673275/how-do-i-fix-an-invalid-license-data-reinstall-is-required-error-in-visual-c

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

[image: continuoustests zip file cannot be opened 2015-09-29-12-05]
https://cloud.githubusercontent.com/assets/795941/10222283/2163b956-6821-11e5-9799-5501b738753d.jpg


Reply to this email directly or view it on GitHub
#18 (comment)
.

@mkamoski
Copy link
Author

mkamoski commented Oct 1, 2015

FYI, I re-ran the ...\ReleaseBinaries\Installer\ContinuousTests-v1.0.48.exe file with the "Run As Administrator" option.
I did NOT get the Invalid License Data error but I did get a freeze on "Resetting addin" still.
Just thought I would mention it.
HTH.
Thanks.
-- Mark Kamoski

continuoustests stuck resetting addin 2015-10-01-10-53

@gregoryyoung
Copy link
Member

Resharper installed by chance?

On Thu, Oct 1, 2015 at 3:57 PM, Mark Kamoski [email protected]
wrote:

FYI, I re-ran the
...\ReleaseBinaries\Installer\ContinuousTests-v1.0.48.exe file with the
"Run As Administrator" option.
I did NOT get the Invalid License Data error but I did get a freeze on
"Resetting addin" still.
Just thought I would mention it.
HTH.
Thanks.
-- Mark Kamoski

[image: continuoustests stuck resetting addin 2015-10-01-10-53]
https://cloud.githubusercontent.com/assets/795941/10224273/3d4b1286-682b-11e5-802f-63cb79057fa8.jpg


Reply to this email directly or view it on GitHub
#18 (comment)
.

Studying for the Turing test

@mkamoski
Copy link
Author

mkamoski commented Oct 1, 2015

gregoryyoung (and all) --
No I do not have ReSharper installed.
But, it appears that the installation actually succeeded, in that it seems to be in Program Files x86.
I then tried this workaround, as suggested above.

http://blog.jessehouwing.nl/2013/12/enabling-mighty-moose-for-visual-studio.html
Enabling Mighty Moose for Visual Studio 2013

And, as far as I can tell, the thing is working.
Thanks so much.
Will start a new issue thread if I find something else from here on because this one is done.
AFAIAC, this issue is CLOSED.
Thanks.
-- Mark Kamoski

@gregoryyoung
Copy link
Member

So normally when you get a hang like that something installed into VS
(other plugins etc) are putting up a modal dialog (R# is the most common
one that does this). Everything else worked its just VS will never close
(its being run in the background to install the plugin)

On Thu, Oct 1, 2015 at 4:11 PM, Mark Kamoski [email protected]
wrote:

gregoryyoung --
No I do not have ReSharper installed.
But, it appears that the installation actually succeeded, in that it seems
to be in Program Files x86.
I then tried this workaround, as suggested above.

http://blog.jessehouwing.nl/2013/12/enabling-mighty-moose-for-visual-studio.html
Enabling Mighty Moose for Visual Studio 2013

And, as far as I can tell, the thing is working.
Thanks so much.
Will start a new issue thread if I find something else from here on
because this one is done.
AFAIAC, this issue is CLOSED.
Thanks.
-- Mark Kamoski


Reply to this email directly or view it on GitHub
#18 (comment)
.

Studying for the Turing test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants