I am starting this discussion because I am getting this error for Team Foundation Server whenever I try to access the website code for the company I work for. My project leader has already assigned me the same permissions as those who are currently on website development but I continue to be restricted. I can try and access the Source Control Explorer through Visual Studio but it just shows up empty (when it shouldn't). I tried reinstalling Visual Studio multiple times and tried installing the license key via the storePID executable through an admin cmd prompt in an attempt to update my access to the website code on tfs.

Any help is appreciated,

Thanks!

↧

build throws an error "Object reference not set to an instance of an object"

June 15, 2019, 6:38 am

≫ Next: Purpose of debug and release configurations

≪ Previous: Error - TF400409: You do not have licensing rights to access this feature: Code

I'm developing an UWP app. Suddenly VS2017, at build or rebuild, throws an error with no specific line of code, at no specific file

"Error Object reference not set to an instance of an object."

Every time I hit build this error is thrown, and unables me to make the build, and run a debug instance.

Also there is another symptom: all .xaml files, with their associated .cs files. at the .cs file, there is the constructor that calls InitializeComponent() method, all .cs files throws the error that can't find the InitializeComponent() method, (or any property/visual control declared in the xaml file)
for example for app.xaml. build throws the error : "Error CS1061 'App' does not contain a definition for 'InitializeComponent' and no accessible extension method 'InitializeComponent' accepting a first argument of type 'App' could be found (are you missing a using directive or an assembly reference?) "

but these error of missing InitializeComponent() method, ONLY appears when a class is shown in documents tabs in the IDE. as soon I close the document, error go away. still the first error descripted above "Object reference not set to an instance of an object" still is there, and disallows me to build my project.

I already tried:

1) rebuild solution
2) clean solution
3) rebuild project
4) clean project
5) revert to a previous commit (known to be working)
6) close and reopen VS
7) reboot the machine
8) update VS2017 to a newer version
9) repair VS2017 with the installer
10) try on another computer
11) target project to a different version of win10. (now targeting 1809)
12) Update VS2017 to VS2019

13) delete completely the project source files, and clone again from gitlab

none of those did work.

what can I do?

I don't know what else I could try, only thing I think, is to rebuild the project from the ground up, with all classes.

↧

Purpose of debug and release configurations

June 18, 2005, 1:51 am

≫ Next: A build controller or agent's status changes notification not working

≪ Previous: build throws an error "Object reference not set to an instance of an object"

Hi there!

I have posted the same question before without finding an anwser. After spending some time with VS I may now be more exprerienced to phrase the question better! Smile The following applies to VS2005 beta 2. Follow the steps:

Open VS and create a new windows app (I use VB but I guess the same goes for C#)
Hit F5 to run the application. The following files are created under bin\debug:
- WindowsApplication1.exe
- WindowsApplication1.xml
- WindowsApplication1.pdb
- WindowsApplication1.vshost.exe
Now hit Ctrl+Shift+B to build the application. The following files are created under bin\release (vshost.exe is missing):
- WindowsApplication1.exe
- WindowsApplication1.xml
- WindowsApplication1.pdb
Close VS, open it again, load the same project and hit Ctrl+Shift+B to build once more. Now all the files are created under bin\release, including vshost.exe!!!

QUESTION1: What's pdb file is doing in the release folder? Isn't it only for debug purposes?
QUESTION2: Why is vshost.exe created in the release folder? And why only the second time? Is it a bug?
QUESTION3: Provided the development process of a specific application does not require any different configuration settings for the debug and release versions, is there a meaning having both these configurations? If you sent the project's output to a colleague to use it would you sent the debug or the release version? (remember, they both include the pdb file).

Thanks,
Dimitris

↧

A build controller or agent's status changes notification not working

July 2, 2019, 12:17 am

≫ Next: Build Agent goes offline after closing run cmd window

≪ Previous: Purpose of debug and release configurations

Hi All,

We used a TFS in-built notification to know the status of agents. But we didn't receive any email notification when we change the agent status.

In-built notification: A build controller or agent's status changes (query fields- when status changes it should notify us)

TFS version: TFS 2018 update 1

Email notification is working fine as we tested with work item change notification.

Query: is the state of agent in TFS andstatus in agent server are same or not ??

Can someone please help on our issue.

Regards,

Rajukumar

↧

Build Agent goes offline after closing run cmd window

July 2, 2019, 12:06 pm

≫ Next: error MSB4062: The “GetOutOfDateItems” task could not be loaded from the assembly

≪ Previous: A build controller or agent's status changes notification not working

I set up a vNext build agent in windows 10 machine. also while configuring the agent i did "Yes" for 'run as service' , but still when i close the run cmd the build agent goes offline. i tried checking in the local services, but even when the run cmd window is running, i dont see any services related to buildagent.

↧

error MSB4062: The “GetOutOfDateItems” task could not be loaded from the assembly

July 1, 2019, 5:55 am

≫ Next: Check certain files are EmbeddedResource

≪ Previous: Build Agent goes offline after closing run cmd window

I am getting following error while building in MSFT VS 2017 using cmake.

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(181,5): error MSB4062: The "GetOutOfDateItems" task could not be loaded from the assembly C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.Build.CppTasks.Common.dll. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

I found a link that says (https://developercommunity.visualstudio.com/content/problem/341712/error-msb4062-the-getoutofdateitems-task-could-not.html) that fix for it is available in VS 2019, but I cannot move to VS 2019 and want to get it to working on VS 2017. Also I am not able to locate which file to edit for including suggested changes at the link. Could one please provide some workaround for VS 2017?

↧

Check certain files are EmbeddedResource

June 9, 2019, 6:29 am

≫ Next: error MSB6003: The specified task executable "cmd.exe" could not be run.- The specified path, file name, or both are too long

≪ Previous: error MSB4062: The “GetOutOfDateItems” task could not be loaded from the assembly

Hello

I need to have a Pre-Build event that checks if all .sql files in a .csproj are included withBuildAction type of 'EmbeddedResource'. If any .sql file is not set as 'EmbeddedResource' a Buid error should be shown in output.

Is there any command for this? Should I implement a custom command line tool to call before build?

Jalalx

↧

error MSB6003: The specified task executable "cmd.exe" could not be run.- The specified path, file name, or both are too long

July 3, 2019, 8:08 pm

≫ Next: Trying to build a gRPC example. How to solve?

≪ Previous: Check certain files are EmbeddedResource

I am generating the vcproject from cmake. While building the generated project I am getting below error.
This error used to come in past in my system, but went off after I re-generated through cmake, but this time it seems stay permanently .

The full error message is like this...

error MSB6003: The specified task executable "cmd.exe" could not be run. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Generated path for projects : C:\Development\projs\build-rel

↧

Trying to build a gRPC example. How to solve?

June 28, 2019, 1:12 am

≫ Next: How to set MSBuild to compile multiple times?

≪ Previous: error MSB6003: The specified task executable "cmd.exe" could not be run.- The specified path, file name, or both are too long

I tried to build a gRPC sample GreeterProtos using Visual Studio 2017, but it fails proceeding with the shell script:

Part of the .csproj file:

<Target Name="GenProtos" BeforeTargets="BeforeBuild" Inputs="@(Proto)" Outputs="@(Generated)">
    <Message Text="Generating protos @(Proto)" Importance="High" />
    
    <Exec Command="$(ProjectDir)..\..\tools\gen_protos.sh" />
    
    <ItemGroup Condition="@(Compile)" == ''">
      <Compile Include="generated\*.cs" />
    </ItemGroup>
</Target>

Error:

Error MSB3073 The command "D:\BHiep\New Workspace\grpc-samples-dotnet-master\grpc-samples-dotnet-master\dotnet_core\Greeter\GreeterProtos\..\..\tools\gen_protos.sh" exited with code 9009.

↧

How to set MSBuild to compile multiple times?

July 9, 2019, 2:52 am

≫ Next: visual studio 2019 produces error while trying to build .exe file from .cpp file

≪ Previous: Trying to build a gRPC example. How to solve?

In our current product, we have multiple solution files of visual studio and multiple projects in them.

In those, few of the solutions .sln files may fail some times and if we retry , they will be successful.

So, we are using devenv.com till date and retrying for 5 times, if it fails on 5th time, we are failing the build job.

But how to integrate this in MSBuild script. Like, we can use msbuild to build the project but how to set the retry attempts to till 5 and do the build process.

Is there any .msbuild script you can suggest for this.

↧

visual studio 2019 produces error while trying to build .exe file from .cpp file

July 10, 2019, 6:45 am

≫ Next: Error MSB3073

≪ Previous: How to set MSBuild to compile multiple times?

Hello Everyone

I just installed Visual Studio 2019 and write a C++ Program. When I tried to debug it and pressed <F5> Key to compile.

It produces an error saying that .EXE File not found.

I don't recognize the problem. Please help.

Thanks

Deepak Kharpate

↧

Error MSB3073

July 10, 2019, 10:37 pm

≫ Next: VS2017 issues with KMDF driver build for Windows 7

≪ Previous: visual studio 2019 produces error while trying to build .exe file from .cpp file

Error MSB3073 The command ""C:\Users\username\.nuget\packages\gulp.js\1.0.2\build\..\tools\npm.cmd" install gulp gulp-util --save-dev" exited with code 1. projectname C:\Users\\username\.nuget\packages\gulp.js\1.0.2\build\gulp.js.targets 12

↧

VS2017 issues with KMDF driver build for Windows 7

July 5, 2019, 1:04 am

≫ Next: TFS Build NodeJs application using Verdaccio (Private repository)

≪ Previous: Error MSB3073

Hi,

I am trying to build my driver for Windows 7. I have changed settings in solution property page to WDK 8.1 and toolkit to v120. After changes I am no longer able to open solution properties and pops up warning information: "There are no property page for the selection." If I try to compile solution I get error message in console: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Redirect.12.props(51,3): error MSB4019: The imported project"C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.cpp.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk."

I tried to reinstall WDK 8.1, SDK's with no help. I have installed VS2013 - no help. I am running out of ideas what to do. Any thoughts how can I compile driver for Win7?

Cheers.

Edit: I have newest release of VS2017 and I am working on Windows 10.

Edit2: I have tried to reinstall SDK 8.1 and after reinstallation I am no longer able to chose it from Platform Toolset field however it does appear in VS Installer as installed component.

↧

TFS Build NodeJs application using Verdaccio (Private repository)

July 11, 2019, 5:22 am

≫ Next: Failed to Sign

≪ Previous: VS2017 issues with KMDF driver build for Windows 7

Hi,

I am trying to use Verdaccio as private NPM repository and build NodeJs application using Team Foundation Server. We have all installation ready with Verdaccio, but unable to use Verdaccio as private repository when creating build.

I have installed Verdaccio and completed steps to set up registry on TFS Server, using below command. Does anyone has done configuration on TFS? i need to know configuration for Verdaccio.

npm set registry http://localhost:4873/

↧

Failed to Sign

July 11, 2019, 10:55 am

≫ Next: VS2019: Choose - When Condition=" '$(Configuration)'=='MyConfig' " not working anymore

≪ Previous: TFS Build NodeJs application using Verdaccio (Private repository)

SeverityCodeDescriptionProjectFileLineSuppression State
ErrorAn error occurred while signing: Failed to sign bin\Debug\app.publish\ SignTool Error: No certificates were found that met all the given criteria.

Would anybody be able to help me with this?

It was originally written in VS2017.

Just opened it in VS2019 and tried to compile and run it. This is the error I received.

↧