Messed up machine configuration file ?

Question

0.00/5 (No votes)

See more:

I'm using both studio.net 2013 and 2019 for coding (mostly 2013 as it just runs faster).
Since a couple of days, I'm now running into an issue using 2013 (using the same solution). 2013 can't find (or has access) to component/ reference (that I know is there).

I understand that both 2013 and 2019 use their own setup config files - making me believe the 2013 setup file somehow got corrupted on my machine.

Question:
Would copying a 2013 setting form another machine potentially fix this or is this machine (PC) dependent?
How do I approach this without creating more issues? What local file should I look at?

Should I start digging around the machine configuration file?

LOG: This bind starts in default load context.
LOG: Using application configuration file: C:......................
LOG: Using host configuration file: 
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.

What I have tried:

I have tried re referencing the component - as expected, that didn't help.

Posted 22-Oct-23 10:37am

Georg Kohler

Updated 24-Oct-23 1:01am

Deeksha Shenoy

v2

Add a Solution

Comments

Dave Kreskowiak 22-Oct-23 16:56pm

I suspect replacing the machine.config file isn't going to do anything.

What's the exact error message you're getting and which component?

[no name] 22-Oct-23 18:48pm

https://visualstudio.microsoft.com/vs/older-downloads/

Georg Kohler 22-Oct-23 23:55pm

it would not let me post this initially
below is the error message

=== Pre-bind state information ===
LOG: DisplayName = Cognex.Explorer.Support, Version=5.4.471.0, Culture=neutral, PublicKeyToken=6b9774afddb09935
 (Fully-specified)
LOG: Appbase = file:///C:/DEV2_KOHLER/_KDM_DEV/_KDM20_5717_TUBEWELDER/bin/
LOG: Initial PrivatePath = NULL
Calling assembly : Cognex.InSight, Version=5.4.471.0, Culture=neutral, PublicKeyToken=6b9774afddb09935.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\DEV2_KOHLER\_KDM_DEV\_KDM20_5717_TUBEWELDER\bin\Kohler Motion Control.vshost.exe.Config
LOG: Using host configuration file: 
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: Cognex.Explorer.Support, Version=5.4.471.0, Culture=neutral, PublicKeyToken=6b9774afddb09935
LOG: Attempting download of new URL file:///C:/DEV2_KOHLER/_KDM_DEV/_KDM20_5717_TUBEWELDER/bin/Cognex.Explorer.Support.DLL.
LOG: Attempting download of new URL file:///C:/DEV2_KOHLER/_KDM_DEV/_KDM20_5717_TUBEWELDER/bin/Cognex.Explorer.Support/Cognex.Explorer.Support.DLL.
LOG: Attempting download of new URL file:///C:/DEV2_KOHLER/_KDM_DEV/_KDM20_5717_TUBEWELDER/bin/Cognex.Explorer.Support.EXE.
LOG: Attempting download of new URL file:///C:/DEV2_KOHLER/_KDM_DEV/_KDM20_5717_TUBEWELDER/bin/Cognex.Explorer.Support/Cognex.Explorer.Support.EXE.

Richard Deeming 23-Oct-23 7:47am

That's not the error message; that's part of the assembly probing log.

And it's nothing to do with the machine configuration, or Visual Studio. It's simply unable to load a third-party assembly from your application folder.

Dave Kreskowiak 23-Oct-23 15:20pm

The messages at the bottom of what you posted just describe where the probe is looking for the file and which filename it's looking for.

Either the file is not there, or the .DLL is not of the correct architecture, or a dependency that .DLL requires is not available.

There is nothing in the machine.config that is going to fix that.

Member 15627495 23-Oct-23 8:42am

don't forget you can reload / repair / reinstall your VS Studio at any time.
a broken setup is to be replace, by the same one.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Georg Kohler · Answer 1 · 2023-10-23T09:35:00

Solution 1

Resetting the Studio settings and reloading settings from another computer somehow fixed it

Thanks for all the Inputs

Posted 23-Oct-23 9:35am

Georg Kohler