Discover Top Posts Tagged with #vs2010

Popular Recent

C# VS2010代码智能补全

IntelliSence·我的习惯是使用智能代码补全时候用【Tab】键，其他时候（比如智能补全不满意，或者有意书写）用【;】键或者空格。

·我的VS2010在任何时候都是用智能补全的代码。不爽。

·设置：编辑-IntelliSense - 切换完成模式。改成只有输入【Tab】键才选用智能补全代码，这下可以随心输入变量名称神马的了。

#切换完成模式 #C #mQney #VS2010 #代码智能补全

vs2010 怎样设置文本编辑窗口和解决方案资源管理器同步？

不能上图，我就直接说了工具--选项--项目和解决方案--常规--在解决方案资源管理器中跟踪活动项（前打勾）确定应该就可以了。

#编辑窗口同步方案资源 #vs2010 #C #zhaopianer.com #mqney.com #yqung.com #zhaopianer #mqney #yqung #tijianren #tijianren.com

Bestehende VS2010 Projekte in Qt Projekte umwandeln

Seit kurzem stehe ich vor dem Problem mich intensiv mit Qt auseinander setzen zu müssen. Da das tolle Qt Plugin für VS2010 es einem nicht erlaubt, ein bestehendes Projekt mit ein paar klicks zu einem Qt Projekt zu machen, hier eine kurze Anleitung.

1. *.vcproj anpassen

Als erstes muss man die *.vcproj mit dem Texteditor anpassen, so dass sich das Qt Plugin überreden lässt, den Menüpunkt zur Umwandlung anzuzeigen. Dazu die Datei einfach mit einem beliebigen Texteditor öffnen und nach PropertyGroup Label="Globals" suchen. Zwischen die beiden Tags muss nun <Keyword>Qt4VSv1.0</Keyword> eingefügt werden, so dass es am Ende in etwa so aussieht:

2. Projekt umwandeln

Einfach das Projekt in VS2010 öffnen und das Projekt über das Contextmenü (das Qt Plugin muss installiert sein) in ein Qt addin project umwandeln. Anschließend kann man in den Qt Project Settings die gewünschten Module freischalten.

3. Includes eintragen

In den Properties des Projektes müssen nun noch die korrekten Pfade eingetragen werden.

Properties -> VC++ Directories -> Include Directories -> $(QTDIR)\include hinzufügen

Properties -> C/C++ -> General -> Additional Include Directories -> $(QTDIR)\include hinzufügen

Properties -> Linker -> Additional Library Dependencies -> $(QTDIR)\lib hinzufügen

#Qt #VS2010

So I was scratching my head the whole evening trying to figure out why I got this error and how to fix it on vb.net project - BadImageFormatException: An attempt was made to load a program with an incorrect format.

Alright, here we go.. the solution that works for me:-

http://blogs.msdn.com/b/visualstudio/archive/2010/06/19/resgen-exe-error-an-attempt-was-made-to-load-a-program-with-an-incorrect-format.aspx

#life of a programmer #vs2010

Visual Studio 2010 Solution: The referenced component 'System' could not be found.

I loaded up a project today that as of yesterday worked 100% ... and recieved an error:

The referenced component 'System' could not be found.

What?! Hold on... let me go into the project properties... oh wait, I can't:

Could not resolve mscorlib for target framework '.NETFramework,Version=v3.5'. This can happen if the target framework is not installed or if the framework moniker is incorrectly formatted.

Thanks! I'll check the .NET installations, reinstall everything, and try again... or not, I got the same error even after adjusting the .NET framework manually in the file. I finally figured it out, eventually: Problem: I had been using remote debugging. The network share I was publishing to and testing from, was no longer available as I had just received a new server at work and I switched everything over yesterday, but had not relaunched the projects since earlier that morning... and they compiled fine after I moved everything somehow. A bug? I would say so... Give me some sort of REAL response to go off of, like "Hey, you idiot, change your output directory." Solution: I went in to my csproj files and cleared out any references to the network shares in all areas of the configuration. Voila! I'm interested to see if anyone else has this problem.

#net #solution #visual-studio #vs2010

Visual Studio 2010 Beta 2: MSHelpListener.exe has stopped working fix

I installed VS2010 Beta 2 today... after uninstalling Beta 1 -- to do which I had to remove the TFS Object Model package FIRST, due to an error I was getting about a missing "tfsobjectmodel-amd64_enu.exe" Everything installed OK, until the end when I tried to install the help files... I got the error: "MSHelpListener.exe has stopped working" Apparently, it tries to bind to port 80, which in my case is already bound to by Skype. Here's the details / fix from the Help Listener documentation:

If port 80 is used by another process (not via the http.sys service) then the Help listener will not be able to attach and use port 80 and will fail. The port number can be changed by adding a string registry value ListenerPort under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help3 with the value of the port to use (eg. 81). Due to the http.sys ACL settings it is necessary to run the following http.sys configuration command from an admin elevated command line. On Vista, Win2k8, and Windows 7 run the following native command: netsh http add urlacl url=http://127.0.0.1:<port number>/help/ sddl=D:(A;;GX;;;WD) On Windows Xp, and Win2K3 run the following command: httpcfg set urlacl /u http://127.0.0.1:<port number>/help/ /a D:(A;;GX;;;WD) If the command is not found then it might be necessary to download the httpcfg.exe from Microsoft as part of the Windows XP Service Pack 2 support Tools (http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en). Now the Microsoft Help Listener will run on the selected port number.

#duh #microsoft #programming #vs2010

Visual Studio 2010 x Ícones de Forms (My.Resources.Resources has no property named)

Tenho um grande projeto em Visual Basic .NET que veio do Visual Studio 2005 para o 2010. Não tive grandes problemas, mas em um form ou outro, comecei a receber a seguinte mensagem:

My.Resources.Resources has no property named 'xxxx'

onde 'xxxx' era o nome do recurso (resource) que o Designer do VS não encontrava. No meu caso, ícones de botões.

Quando essa mensagem aparece, você precisa clicar em Ignore pra poder visualizar o form, que virá sem os referidos recursos, no meu caso, sem os ícones.

Resolvi esse problema, a partir da seguinte dica:

Procurar no References por alguma referência ao seu próprio Assembly. Ou seja, ver se o projeto está referenciando o executável ou dll que ele mesmo gera.

Se estiver, é só remover e o Designer para de se perder com os Resources.

No meu caso, resolveu.