43

I recently added some of my Visual Studio 2010 projects to a solution, and now every time I reopen the program they stop compiling. They complain "Unable to open module file C:\Users[USERNAME]\AppData\Local\Temp\1.NETFramework,Version=v4.0.AssemblyAttributes.vb. System cannot find the file specified." I've checked, the file exists and is accessible from the VS Editor itself!

All the information about this error I've found recommends using rebuild to work around the issue. That works for me, but I would rather not have to run a rebuild the first time I open every one of my solutions! Is there someway to avoid this error?

Improve this question
6
  • The \1\ looks like a remote desktop Session ID. When you log off, the Session is removed. Commented Jun 11, 2011 at 19:44
  • 1
    It is a little helper file that the IDE generates to help the IntelliSense parser figure out what target framework was selected. This is an environmental problem, hard to guess what's wrong with your machine. You'd better check out what is all getting started up automatically when you reboot. Use SysInternals' AutoRuns Commented Jun 11, 2011 at 19:52
  • @vcsjones, I am accessing the development box via RDC, so you probably have the problem right. Is there a way to avoid this file being created/needed when in a Remote environment? Or to recreate it automatically on logon? Commented Jun 12, 2011 at 18:32
  • 2
    I get this and I don't use RDC (my path stops at \Temp), any other suggestions as to what causes it? Commented Aug 23, 2012 at 14:54
  • 1
    @BlackICE: The problem occurs because Visual Studio generates it when you build, and Visual Studio assumes that if a .suo file exists for your solution, then that file must also exist. Anything that cleans up the TEMP folder can delete that file, and cause the problem. RDC makes this much more visible because it happens to create/delete a TEMP directory on login. Commented Aug 30, 2016 at 21:26

9 Answers 9

Reset to default
73

Yes, this is a problem caused by Remote Desktop Connections. RDC is (by default) setup to use create a new directory each time you log in remotely. Also, it's setup (separate setting) to delete that directory once you log off. The real solution is to remove these two settings so that it will just use your standard Temp folder, not deleting the files at logout.

There are also two workarounds to this problem:

  1. Workaround 1: Delete your .suo file for the solution before opening the solution or rebuilding.
  2. Workaround 2: Use the "Rebuild All" option for the fix

Note: Setting up RDC can really only be done if you're logged on as an administrator on the box, thus, the two workarounds.

Improve this answer
Sign up to request clarification or add additional context in comments.

7 Comments

Where are these settings located?
@just.another.programmer Configure Temporary Folders for an RD Session Host Server. (In case the link dies) They're in the control panel: Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration
Not necessarily caused by RDP, but that is the most common, and is recognizable by the \1\ in the path. In my case, my Temp directory was emptied last week by the Windows 10 update to build 15063. Disk cleanup can do it too, if you put a check mark at 'Temporary Files'. And I guess I don't need to tell you to steer clear of those system cleaners and optimizers certain web sites spam you about.
The .suo file will be saved in the folder where your Solution (.sln) file exists. You might wanted to set true for “Show Hidden Files and Folder” in “Folder Options” as .suo file is default by hidden. C:\~\Solution.sln\.vs\SolutionName\v14
I'm using VS2017: deleting the .vs folder did it for me. It may be that deleting just the .suo file in that tree would be more precise.
|
6

I restarted visual studio and that did the trick...

Improve this answer

Comments

3

It is a bug in the Visual Studio 2010. Clean and build works for me.

Improve this answer

1 Comment

Not just vs 2010. Same issue in 2015
3

In my case VS couldn't access to users TEMP folder. After changing permissions to allow all users (my computer has one user - me) full control over this folder, everything was fixed.

Hope this will help.

Improve this answer

1 Comment

This was the problem I had, C# solution not VB but same deal.
3

Another option is to create the desired files at the desired location. That would be:

"C:\Users\user\appdata\local\temp\1.NETFramework,Version=v4.0,Profile=Client.AssemblyAttributes.cs" with the following content:

// <autogenerated /> using System; using System.Reflection; [assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.0,Profile=Client", FrameworkDisplayName = ".NET Framework 4 Client Profile")]

"C:\Users\user\appdata\local\temp\1.NETFramework,Version=v4.0.AssemblyAttributes.cs" with the following content:

// <autogenerated /> using System; using System.Reflection; [assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.0", FrameworkDisplayName = ".NET Framework 4")]

"C:\Users\user\appdata\local\temp\1.NETFramework,Version=v4.0.AssemblyAttributes.vb" with the following content:

Option Strict Off Option Explicit On Imports System Imports System.Reflection <Assembly: Global.System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.0", FrameworkDisplayName:=".NET Framework 4")>

for other version of .NET, just change the version in the file contents e.g.

[assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(".NETFramework,Version=v4.5", FrameworkDisplayName = ".NET Framework 4.5")]
Improve this answer

1 Comment

The error message might disappear, but I encountered other strange problems, i.e. Visual Studio 2015 did not change my settings for debug output filtering which was pretty annoying, after configuring tempory folders the problem went away.
2

I deleted the AssemblyAttributes.vb file and it magically got recereated. that's how I solved.

Improve this answer

1 Comment

This works for me. Not sure how but after delete, I've clean and rebuild and works fine.
1

Do not open the solution directly from the visual studio 2010. open the solution by clicking the project solution file from the folder where the project has been saved.

its resolved my problem...

Improve this answer

1 Comment

I wonder what about that would solve the problem described here.
0

Like vcsjones said, it looks like a problem with RDC. It fixed itself after I closed my RDC session and reset the terminal server.

Improve this answer

Comments

0

Make sure that your drive have enough free space. I have experienced the same issue, resolved after allocating more free space in the drive

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.