ISDEV : error : -6225: Resolving Visual Studio .NET project output - by Jignasu Khant

Status : 

 


1
0
Sign in
to vote
ID 785629 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 4/25/2013 4:44:13 PM
Access Restriction Public

Description

I am using Visual Studio 2012 (VS) and IS 2012 SE. I have created a Basic Setup Project in VS and it is working fine. But when I use VS command line tool to build the project I am getting below error.

 ISDEV : error : -6225: Resolving Visual Studio .NET project output "MyProject\MyProject.csproj\|Built"

 Here is what command at command line looks like.

 devenv.com /build "Debug|Any CPU" "C:\Build\Full Project Path\MySolution.sln"

 Can you please help resolve this error?

---------------------------------------------

I am also getting error when building a WebSite using devenv.com.  It is having trouble resolving references.  When build from IDE it is working fine.  The exact error message I am getting is below.

19>------ Build started: Project: http://localhost/WebSite1/, Configuration: Debug Any CPU ------

19>Could not get dependencies for project reference 'ReferenceAssembly1'Could not get dependencies for project reference 'ReferenceAssembly2'Could not get dependencies for project reference 'ReferenceAssembly3'Could not get dependencies for project reference 'ReferenceAssembly4'Could not get dependencies for project reference 'ReferenceAssembly5'Could not get dependencies for project reference 'ReferenceAssembly6'Could not get dependencies for project reference 'ReferenceAssembly7'Could not get dependencies for project reference 'ReferenceAssembly8'Validating Web Site

 Thanks
 Jignasu 
Sign in to post a comment.
Posted by dcarlson661 on 8/22/2014 at 11:02 AM
CLOSED! WTF Microsoft has turned into such a heap. This Must be fixed. I would suggest dumping the installshield excrement and going back to the MSI build from vs2008. Stop listening to your dummy programmers that you hired away from Google and get some seasoned veterans in there.
Posted by Microsoft on 4/30/2013 at 2:54 PM
Hi Jignasu,

Unfortunately this issue occurs because of a change we made in how we build our projects that Flexera was unable to work around. We will not be addressing this issue as the workaround is to use MSBuild from the command line instead of devenv.

Thanks,

Tony Goodhew,
Program Manager, VS Pro.
Posted by Microsoft on 4/26/2013 at 12:06 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 4/25/2013 at 5:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)