visual studio 2012 - VS2012 Project Reference's Properties' path does not match .vbproj HintPath -

-

My goal was to update a reference to a new version from my old DLL that was updated in VS2012.

D: \ God \ & lt; Old_path & gt; \ TEST \ bin \ Company.dll D: \ DEV \ & lt; New_path_2012 & gt; \ TEST \ bin \ Company.dll

In the .vbproj file ... 

  & lt; Include references = "company, version = 0.0.0.0, culture = neutral" & gt; & Lt; SpecificVersion & gt; False & lt; / SpecificVersion & gt; & Lt; HintPath & gt; .. \ .. \ & LT; New_path_2012 & gt; \ Test \ bin \ Company.dll & lt; / HintPath & gt; & Lt; / References & gt;

In the Solution Explorer, under context, I right-click on the context of the company and click Properties. The path is listed as ... 

  D: \ DEV \ & lt; Old_path & gt; \ TEST \ bin \ Company.dll \ n \ / code>

There are no errors or warnings are appearing to produce everything properly, but due to this discrepancy, I lack the confidence. How can I fix this?

I tried to restart VS 2012 and tried to remove TFS cache. The problem is being solved by downloading a new copy of this project from TFS on another PC, but I want to understand better how to solve it without such harsh measures.

I just crop this issue, and it was an old thread, while this was the first Google result When I did my search, I thought what had happened to me.

TL; DR: Check the triple gesture path - this could be wrong, and using DLL in VS GAC

My problem came because I was using a little script to send me more than 250 projects My hint path was 'right' at first sight, but to help in updating the issues, and in a small handful that did not follow the normal folder layout, because it was not really, VS 2013 went to the version of DLL in GAC.

Once that was wrong, I decided that the project file, the relative path to the gesture path and the context which was displayed in the context was matched.

< / Div>

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more