Ошибка визуал студио

We are currently evaluating the new Visual Studio 2015 and encountered a strange problem with IntelliSense. When I compiled our main solution with the new studio the build succeeds, but nevertheless 6 errors are shown.

I discovered that it’s not a real error, but only an intellisense error. The code is definitely correct and everything compiled successfully. The code however is marked red and errors show up in the error list.

All 6 errors have the same origin. It’s a simple constructor call. Strange enough, but there are also some occurrences of the exact same constructor without any errors.

The error message:

Code: CS1729
Message: '<the class>' does not contain a constructor that takes that many arguments.
Project: <the project name>
File: <the path to the file>

The new studio was installed on a freshly installed Windows 7 without any legacy software (no VS13).

I’ve already tried to clear the caches, deleted the suo file, deleted bin and obj directories, cleaned and rebuilt the solution etc. But nothing worked.

Can anyone explain that behavior to me?

Also had this problem with a migrated project, so I referenced the Microsoft.CSharp dll. In some projects I needed to remove and add again the Reference in the project.

Also had this problem (the title, not the specific error message), as well as squiggly lines in the editor. The first squiggly line is under the first #include statement, which names a precompiled header. Intellisense fails to include the precompiled header, but doesn’t list that as an error; instead it lists errors further down the file, on code that (very rightfully) relies on declarations in the precompiled header.

The reason Intellisense doesn’t find the precompiled header in my environment is that the header named is not an actual file. It doesn’t have to be in any other VC or gcc version I used, nor in the 2015 compiler, as long as the precompiled header settings are correctly configured. Apparently not any more for Intellisense. I’m not entirely sure it was different in 2013, maybe I just never noticed.

In the unlikely case that this would be the problem reported here, the solution is simple: create a small file with the pretend-name of the precompiled header, as specified in #include directives, and let that file include the actual name of the precompiled header.

If you wonder… why this distinction between the precompiled header name in the ‘#include’ statement and the actual filename of the precompiled header? Precisely because it guarantees that precompiled header settings are correctly configured. Wherever a precompiled header is «#included», there is no file around that could be included. Either an actually precompiled (binary) version of the actual header is read, or the compilation fails. Obviously, a disadvantage is that it confuses people reading the code, not just Intellisense.

answered Sep 15, 2015 at 20:55

answered Sep 10, 2018 at 14:46

answered Jan 22, 2017 at 19:40

In Visual Studio 2019 the problem is with changing branches with Git when there are NuGet packages installed in the project. What I did to solve this:

1. Clean Solution
2. Close Visual Studio
3. Delete the packages folder
4. Open Visual Studio
5. Go to Package Manager
6. Restore all packages
7. Recompile
8. If roslyn is missing, close and open Visual Studio, then recompile.

answered Mar 16, 2020 at 15:28

answered May 30, 2017 at 14:56

I had a similar issue with different Visual Studio versions.

Deleting the .suo or .vs folder did not help for me.

The Solution for me was, that I had the Extension StopOnFirstBuildError active. After turning off «Stop build on first error» in the build menu, and after the solution was fully built, the errors shown by Intellisense went away.

answered Mar 13, 2018 at 7:34

I was seeing the intellisearch errors only when publishing a website. (ASP/C# site, VS 2017). They broke the publish. Site ran fine locally.

Cleared the errors by unchecking the setting to pre-compile, and it published fine.
Publish -> Setting -> File Publish Options -> Precompile during publishing

answered May 10, 2018 at 18:02

answered Oct 8, 2021 at 18:50

We are currently evaluating the new Visual Studio 2015 and encountered a strange problem with IntelliSense. When I compiled our main solution with the new studio the build succeeds, but nevertheless 6 errors are shown.

I discovered that it’s not a real error, but only an intellisense error. The code is definitely correct and everything compiled successfully. The code however is marked red and errors show up in the error list.

All 6 errors have the same origin. It’s a simple constructor call. Strange enough, but there are also some occurrences of the exact same constructor without any errors.

The error message:

Code: CS1729
Message: '<the class>' does not contain a constructor that takes that many arguments.
Project: <the project name>
File: <the path to the file>

The new studio was installed on a freshly installed Windows 7 without any legacy software (no VS13).

I’ve already tried to clear the caches, deleted the suo file, deleted bin and obj directories, cleaned and rebuilt the solution etc. But nothing worked.

Can anyone explain that behavior to me?

Also had this problem with a migrated project, so I referenced the Microsoft.CSharp dll. In some projects I needed to remove and add again the Reference in the project.

Also had this problem (the title, not the specific error message), as well as squiggly lines in the editor. The first squiggly line is under the first #include statement, which names a precompiled header. Intellisense fails to include the precompiled header, but doesn’t list that as an error; instead it lists errors further down the file, on code that (very rightfully) relies on declarations in the precompiled header.

The reason Intellisense doesn’t find the precompiled header in my environment is that the header named is not an actual file. It doesn’t have to be in any other VC or gcc version I used, nor in the 2015 compiler, as long as the precompiled header settings are correctly configured. Apparently not any more for Intellisense. I’m not entirely sure it was different in 2013, maybe I just never noticed.

In the unlikely case that this would be the problem reported here, the solution is simple: create a small file with the pretend-name of the precompiled header, as specified in #include directives, and let that file include the actual name of the precompiled header.

If you wonder… why this distinction between the precompiled header name in the ‘#include’ statement and the actual filename of the precompiled header? Precisely because it guarantees that precompiled header settings are correctly configured. Wherever a precompiled header is «#included», there is no file around that could be included. Either an actually precompiled (binary) version of the actual header is read, or the compilation fails. Obviously, a disadvantage is that it confuses people reading the code, not just Intellisense.

answered Sep 15, 2015 at 20:55

answered Sep 10, 2018 at 14:46

answered Jan 22, 2017 at 19:40

In Visual Studio 2019 the problem is with changing branches with Git when there are NuGet packages installed in the project. What I did to solve this:

1. Clean Solution
2. Close Visual Studio
3. Delete the packages folder
4. Open Visual Studio
5. Go to Package Manager
6. Restore all packages
7. Recompile
8. If roslyn is missing, close and open Visual Studio, then recompile.

answered Mar 16, 2020 at 15:28

answered May 30, 2017 at 14:56

I had a similar issue with different Visual Studio versions.

Deleting the .suo or .vs folder did not help for me.

The Solution for me was, that I had the Extension StopOnFirstBuildError active. After turning off «Stop build on first error» in the build menu, and after the solution was fully built, the errors shown by Intellisense went away.

answered Mar 13, 2018 at 7:34

I was seeing the intellisearch errors only when publishing a website. (ASP/C# site, VS 2017). They broke the publish. Site ran fine locally.

Cleared the errors by unchecking the setting to pre-compile, and it published fine.
Publish -> Setting -> File Publish Options -> Precompile during publishing

answered May 10, 2018 at 18:02

answered Oct 8, 2021 at 18:50

I am getting an «Unknown Error» (shown below) alert when I try to launch Visual Studio 2017 Community after successful installation.

UPDATE: After Force uninstall & reinstallation

Please check if the machine has Symantec Workspace Virtualization Agent installed. Removing the product from addremove programs fixed the unknown error while launching VS 2017.

Here is the detail of the product.
Product code: {785F9A4D-D113-43B3-AA1D-77AD777F0A2F}
Package code: {32DB9767-3EF7-465A-ADF2-7ECFD25ABC12}
Install date: 2015.05.21
Version: 6.4.1266
Publisher: Symantec

answered Mar 23, 2017 at 15:22

I fixed it the same way as niclar by deleting folder 15_.*. It does however appear that renaming privateregistry.bin has same effect with less trouble.

As mentioned by Torbjorn, ReSharper and other Extensions can mess up, however no reinstall required.

Merely go to Tools > Extensions and Updates… > Scroll through list of Installed Extensions > Enable those that should be enabled.

answered Apr 11, 2017 at 7:21

answered May 15, 2017 at 8:17

answered Jun 8, 2017 at 16:56

answered Jul 17, 2017 at 21:14

I found same issue after installing the extension and removing the folder «C:UsersUSER_NAMEAppDataLocalMicrosoftVisualStudio15.0_xxxxxxx» solved my problem.

answered May 20, 2020 at 22:44

I am getting an «Unknown Error» (shown below) alert when I try to launch Visual Studio 2017 Community after successful installation.

UPDATE: After Force uninstall & reinstallation

Please check if the machine has Symantec Workspace Virtualization Agent installed. Removing the product from addremove programs fixed the unknown error while launching VS 2017.

Here is the detail of the product.
Product code: {785F9A4D-D113-43B3-AA1D-77AD777F0A2F}
Package code: {32DB9767-3EF7-465A-ADF2-7ECFD25ABC12}
Install date: 2015.05.21
Version: 6.4.1266
Publisher: Symantec

answered Mar 23, 2017 at 15:22

I fixed it the same way as niclar by deleting folder 15_.*. It does however appear that renaming privateregistry.bin has same effect with less trouble.

As mentioned by Torbjorn, ReSharper and other Extensions can mess up, however no reinstall required.

Merely go to Tools > Extensions and Updates… > Scroll through list of Installed Extensions > Enable those that should be enabled.

answered Apr 11, 2017 at 7:21

answered May 15, 2017 at 8:17

answered Jun 8, 2017 at 16:56

answered Jul 17, 2017 at 21:14

I found same issue after installing the extension and removing the folder «C:UsersUSER_NAMEAppDataLocalMicrosoftVisualStudio15.0_xxxxxxx» solved my problem.

answered May 20, 2020 at 22:44