visual-studio-2008-sp1

Fiddler not sniffing SOAP traffic from ASP.NET website

一个人想着一个人 提交于 2019-12-02 15:30:14
So far I've been successfully using fiddler to sniff web service traffic from both test fixtures, console apps and web projects. Today I noticed I am not able anymore to sniff that kind of traffic if I am running my web application (it's a ASP.NET website, hosted locally on IIS). I see all the local traffic but the web service traffic is just gone (the service is being hit as I do see the response debugging into the code). I am still able to successfully sniff soap requests and responses from test fixtures or console apps in the same solution (exact same environment). If it was a windows (I am

Configuring 64-bit compilation inside Visual Studio 2008 Express Edition (VS2008EE)

余生长醉 提交于 2019-11-30 13:49:36
问题 I am making an attempt at building 64-bit native C++ applications under Visual Studio 2008 Express Edition Service Pack 1 (with some relevant Windows SDK(s) installed afterwards), in the IDE and from the command line. This is on a Windows XP Professional x64 Edition Version 2003 Service Pack 2 machine. I know that the Professional versions might provide true VS IDE integration, but I'm specifically looking to do this from within Visual Studio 2008 Express Edition. But, I'm having a bit of

Configuring 64-bit compilation inside Visual Studio 2008 Express Edition (VS2008EE)

♀尐吖头ヾ 提交于 2019-11-30 08:35:01
I am making an attempt at building 64-bit native C++ applications under Visual Studio 2008 Express Edition Service Pack 1 (with some relevant Windows SDK(s) installed afterwards), in the IDE and from the command line. This is on a Windows XP Professional x64 Edition Version 2003 Service Pack 2 machine. I know that the Professional versions might provide true VS IDE integration, but I'm specifically looking to do this from within Visual Studio 2008 Express Edition. But, I'm having a bit of trouble in the project configuration in the Visual Studio 2008 Express IDE, and am hoping someone can

How to make [DebuggerDisplay] respect inherited classes or at least work with collections?

我的梦境 提交于 2019-11-30 08:32:41
I've got a class which inherits from a List<MagicBean> . It works well and as expected in all respects except one: when I add the [DebuggerDisplay] attribute. Even though looking at List has its as [DebuggerDisplay("Count = {Count}")] , if I so much as copy and paste that onto mine, I lose the ability to look directly at all of the MagicBeans I have without drilling into base->private members while debugging. How do I get the best of both worlds? IE: Custom value in the value column, and Visual Studio not hiding my magic beans from me? You can get the effect you need by using the

How can i determine the version of the Windows SDK installed on my computer?

孤者浪人 提交于 2019-11-30 07:49:26
I've very recently decided to teach myself c++ and win32 programming after learning vb.net , and I've got a very simple question: How can I determine what version of the Windows SDK is installed on my computer? I'm asking so I can install the latest version if it isn't installed already, before I start playing around with c++ . I'm using Microsoft Visual Studio 2008 SP1 as my IDE . On English locale at least: dir "%ProgramFiles%\Microsoft SDKs\Windows" should work. It is quite likely that there will be multiple versions installed, which is the right one for an one build can only be specified

Linking Windows DLL files from static libraries using CMake without hand-crafting unresolved symbol names

▼魔方 西西 提交于 2019-11-30 04:34:33
The Situation I'm using Visual Studio 2008 SP1 (Professional Edition, both for 32-bit and 64-bit builds). I'm seeking a workaround to what I believe is a very unhelpful " limitation " in Visual Studio. I find it quite surprising that the Visual Studio linker and compiler does not do this right at DLL file creation time, to automatically scan all specified static libraries for all exported symbols in the same manner given in Building an Import Library and Export File and in a StackOverflow comment . I confirmed that it is not sufficient to simply apply __declspec(dllexport) and __declspec

How to make [DebuggerDisplay] respect inherited classes or at least work with collections?

允我心安 提交于 2019-11-29 11:53:47
问题 I've got a class which inherits from a List<MagicBean> . It works well and as expected in all respects except one: when I add the [DebuggerDisplay] attribute. Even though looking at List has its as [DebuggerDisplay("Count = {Count}")] , if I so much as copy and paste that onto mine, I lose the ability to look directly at all of the MagicBeans I have without drilling into base->private members while debugging. How do I get the best of both worlds? IE: Custom value in the value column, and

How can i determine the version of the Windows SDK installed on my computer?

一笑奈何 提交于 2019-11-29 10:34:39
问题 I've very recently decided to teach myself c++ and win32 programming after learning vb.net , and I've got a very simple question: How can I determine what version of the Windows SDK is installed on my computer? I'm asking so I can install the latest version if it isn't installed already, before I start playing around with c++ . I'm using Microsoft Visual Studio 2008 SP1 as my IDE . 回答1: On English locale at least: dir "%ProgramFiles%\Microsoft SDKs\Windows" should work. It is quite likely

How do I change the working directory while debugging in Visual Studio?

[亡魂溺海] 提交于 2019-11-29 08:18:32
问题 I have a Windows Forms project in Visual Studio that reads configuration files from another project in the same solution. Once deployed, this application will run from the root folder for the solution, and the files will then be read from something like "<Executing assembly path>/Project1/connection.config". When I however debug the Windows Forms application and get the executing assembly path, it will run from "bin/Debug" or "bin/Release", ergo the path to the configuration files is

Linking Windows DLL files from static libraries using CMake without hand-crafting unresolved symbol names

浪子不回头ぞ 提交于 2019-11-29 01:49:12
问题 The Situation I'm using Visual Studio 2008 SP1 (Professional Edition, both for 32-bit and 64-bit builds). I'm seeking a workaround to what I believe is a very unhelpful "limitation" in Visual Studio. I find it quite surprising that the Visual Studio linker and compiler does not do this right at DLL file creation time, to automatically scan all specified static libraries for all exported symbols in the same manner given in Building an Import Library and Export File and in a StackOverflow