Visual C++ Team Blog

Beta2 is generally much better than Beta1(faster and more  stable). But I still have 2 questions:

1. I noticed the ClearType font in TextEditor is better compared with beta1, but I still not feel very comfortable about it. I just feel the font (Courier New) in TextEditor is not as "solid" as it in other part of GUI (like Solution Explorer and Menus). It seems that the  font in TextEditor is not affect by the ClearType Tuner, is that true?

2. When I convert some of my VS2005 project to VS2010, they just can not build, and I found that it is because including the wrong header file. Previously some default include directory are in both include directories and exclude directories but after converting they are removed from the include directories (still in exclude directory). Is that the behavior by design? In my opinion, it cause some inconsistence there.

Anyway, beta2 is awesome, good job!

Windows Embedded CE has a C++ Silverlight port. (http://www.microsoft.com/windowsembedded/en-us/products/windowsce/silverlightforwe.mspx)

Having a native XAML / Silverlight framework would be also beneficial for the Desktop.

This would allow also native developers to develop modern UIs.

If you think that having a native XAML/Silverlight framework for the Desktop is a good idea please sign this petition: http://www.petitiononline.com/SWE4DKTP/petition.html

This is really buggy.  Intellisense is hanging and I have to kill vcpkgsrv or whatever that process is called (filed under connect). It's also ignoring some external build dependencies.  

Is there a way to send my gigantic solution to someone at ms so they can try to build it and iron out all the build issues?

Hello JK,

I'm sorry that you're seeing VCPkgSrv.exe crashing like that.  Needless to say, these crashes are hard to repro without following exact pattern of editing you did or parsing your particular sources.  So, I'm extremely interested in seeing your solution, and use that to iron out issues you're running into.  Can you please email me directly (batul at microsoft . com) and we get a direct conversation going between us in how I can get hold of your sources?

Thanks,

Ulzii Luvsanbat

Windows C++ Team

Here's what I found in a few hours of testing.

Good points about beta 2:

* Didn't hit any compiler issues.

* The CRT regressions I hit earlier have been fixed (i.e. VirtualDub doesn't crash on startup).

* Editor/UI has improved noticeably, with antialiasing quality issues reduced and no more WPF debug D3D errors.

Problem areas:

* The installer reported a failed install due to an error about missing installation media, when I had fixed that and hit Retry, and the installation had succeeded. This happened because the setup program tried to restart after a required reboot before I had a chance to manually remount the ISO.

* The v7.0A Platform SDK introduces a number of issues relative to the one shipped with VS2005, the worst one being that <qedit.h> is missing. It also conflicts with older DirectX SDKs, which can cause problems when settings from older VS versions are imported.

* I hit a weird problem with stale include paths. Somehow, MSBuild was using imported include paths from VS2005 even though the UI didn't show those paths in the property sheet editor for the project or for the user-local property sheet. Editing the user sheet made the problem go away and I can't reproduce it anymore. I suspect this may have been due to the previous VS2010b1 installation (which I uninstalled prior to installing b2).

* Intellisense has some issues -- several times F12 (Go to Definition) brought up a window pane with two blank entries.

* The project system is still quite a mess. Projects converted from VS2005 throw a lot of warnings, and the bug with files that are excluded in a config and have custom build rules still building is still there (reopened). I can't edit All Platforms on a project imported from VS2005 (filed). Relative paths in the output directory cause lots of warnings and problems (already filed). Double quotes in the output list for a custom build rule break post-conversion (not yet filed).

* The new help system is a disaster so far. I tried for about an hour to get any local help to work to no success. The local help installation procedure is byzantine and really needs more status indicators, especially when it is copying or downloading very large files. The server occupies port 80, which is obnoxious if anyone wants to run a local web server for testing. There doesn't appear to be an index. IMO, of all of the areas in 2010, this by far needs the most improvement to reach shippable state.

Hi Phaeron,

I am sorry to hear that you run into these issues with Beta 2. Can you let us know the Connect tickets you opened for the issues you reported?

* Uninstalling Beta 1 indeed will not remove the user props files as they are generated files and they have the potential of interfering with the Beta 2 paths. Resetting the settings or importing from a VS2008 .vssettings should also solve the problem.

* "Exclude from build" should work for Custom Build Rules in Beta 2. Can you try reconverting your projects? They may still point to previously converted rules (from beta 1). If you can still repro this issue, please attach your repro, let me know the ConnectID and we'll take another look at the bug.

* Unfortunately Beta 2 shipped without a path-normalization call during the build that causes unnecessary warnings when using relative paths. This was fixed post Beta 2 but in the meantime we can provide a workaround in the Connect bug.

Thank you for trying out Beta 2 and sending us your feedback!

Marian

@Marian:

There are a few build issues but those were mostly fixed with some code changes.  The big problems are some custom build steps that have bad dependencies and a few paths that aren't converted properly in the project settings

[Alex]

> Except the bug with move constructor/assignment operator in std::function, which are still not there.

This was fixed after Beta 2 branched; the fix will be in VC10 RTM. (regex and match_results were also given move constructors and move assignment operators.)

Did you file a Connect bug about this? I don't see one - we fixed this because I noticed while reading the sources that std::function, regex, and match_results lacked move semantics - i.e. if I hadn't noticed this (and there are lots of things I don't notice), we would be learning about it just now.

Please file Connect bugs when you notice problems! Otherwise, you risk having to wait until the next major version for a fix, and that doesn't make anyone happy.

Stephan T. Lavavej, Visual C++ Libraries Developer

Hi Phaeron,

Regarding your comment: "* Intellisense has some issues -- several times F12 (Go to Definition) brought up a window pane with two blank entries."

We have fixed a bug recently that had the same behavior.  However, I would like to make sure you're not seeing a different bug.  If you haven't already opened a bug through Connect with your source code attached, would you mind sending me something that reproduces what you're seeing?  My email is up there in this blog thread.

Thanks,

Ulzii Luvsanbat

Windows C++ Team

@bjoern

Thanks for the report.  We have recently done another pass over our international resources in MFC and fixed all the layout and clipping issues we found in the dialogs.  These fixes were not in time for Beta2 but will appear in the released version.

Pat Brenner

Visual C++ Libraries Development

Hi,

I have an issue with the current nullptr implementation, which is perfectly described by Fuz in a Channel9 video comment:

"Regarding the problems with nullptr and C++/CLI.  Does this mean that a third-party template library that uses nullptr (rather than __nullptr) in its headers will be unable to be included in any C++/CLI project?

This is a perfectly feasible situation even in interop code, where you have a C++/CLI type wrapping a C++ type which contains a member from this template library.

This would seem to leave the template library little choice but to define a macro to map to either nullptr or __nullptr depending on whether it's a C++/CLI build or not (which it shouldn't care about, since it's a pure C++0x library), which ends up being worse than the NULL macro!"

I believe there must be a better solution, such as a way to select which meaning the nullptr keyword has (managed or native) when /clr is used. Since I'm using the it just for unit tests, all my nullptr occurrences are native, not managed.

Stephan, I filed a bug in Connect for Beta 1 and it was marked as resolved and closed, didn't do it for Beta 2. And, considering your words, it seems there is no need to do it.

One more thing that disturbs me and even looks like became worse in Beta 2 is the speed of native step-by-step debugging with Disassembly View active. It is so slow on quad core with constant updating of Call Stack, Disassembly View, Watch and other windows. I will create a bug in Connect about this.

Will there be another beta after this one?  There are a lot of bugs in Beta 2 and it would help if there was another drop before the release.

Will this ever be fixed?  This goes back to v1.

http://social.msdn.microsoft.com/Forums/en-US/vcprerelease/thread/5ab8c17b-4a71-4cc5-823d-cfb876e3f95b

>There are a lot of bugs in Beta 2 and it would help if there was another drop before the release.

Are there Connnect bugs on all of them to ensure people are aware?  As with all software development there is a release date and some bugs will be deemed not critical to fix before release :(, but ALL bugs we aren't aware of are pretty much guaranteed to be not fixed before release :)

@Phaeron

#http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=456563

I took a look at the bug and the project attached has an import to $(VCInstallDir)VCProjectDefaults\masm.targets rather than $(VCTargetsPath)BuildCustomizations\masm.targets which should be the right path in Beta 2. The .targets/.props/.xml in VCProjectDefaults might be left-overs from Beta 1 where we were incorrectly converting the .rules files in that folder. Can you check that that's the case?

#https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=501105

This issue doesn't repro with our recent builds and should be fixed in RC/RTM. There is a forum thread on this issue where user u0m3 found a possible workaround: http://social.msdn.microsoft.com/Forums/en-US/vcprerelease/thread/d656f92b-bde2-43e0-bce3-5ad6b5b8c9db

@JK

We have a known issues when finding \" in a stringlist, but if you're running into other conversion issues with paths, we'd like to know about them. Same for the custom build step issues. Can you open a connect issue or send me a quick email describing the issues you ran into at mluparu at microsoft dot com?

Thanks,

Marian

@required

A property sheet can be imported in multiple projects thus achieving the exact behavior you're looking for. Using Property Manager you can manage these property sheets.

One of the property sheets you will see automaticall imported in each of your projects is the VCDirectories equivalent called Microsoft.Cpp.$(Platform).props. Making changes (only once) to this file will apply to *all* projects & configurations targeting that platform on that machine/for your user account.

You can find more details about these scenarios in this blog post: http://blogs.msdn.com/vsproject/archive/2009/07/07/vc-directories.aspx

Thanks,

Marian

Thanks "required", "Amit Mohindra"! The changes in VC++ Directories really confused me. I was previously unable to remove the inherited directories! In fact, the topic for "VC++ Directories" is not in the beta 2 help!

http://www.microsoft.com/visualstudio/en-us/products/2010/default.mspx > Compare 2010 Products > Debugging & Diagnostics > Static Code Analysis indicates that /analyze will not be in Professional, but will be in Premium and Ultimate.

[Chris Lux]

> Why is _SECURE_SCL still enabled in Release builds?

It's not:

C:\Temp>cl

Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.21003.01 for 80x86

Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

C:\Temp>type meow.cpp

#include <iostream>

#include <ostream>

using namespace std;

int main() {

#ifdef _DEBUG

   cout << "Debug" << endl;

#else

   cout << "Release" << endl;

#endif

   cout << "IDL: " << _ITERATOR_DEBUG_LEVEL << endl;

   cout << "SCL: " << _SECURE_SCL << endl;

   cout << "HID: " << _HAS_ITERATOR_DEBUGGING << endl;

}

C:\Temp>cl /EHsc /nologo /W4 /MT meow.cpp > NUL && meow

Release

IDL: 0

SCL: 0

HID: 0

C:\Temp>cl /EHsc /nologo /W4 /MD meow.cpp > NUL && meow

Release

IDL: 0

SCL: 0

HID: 0

C:\Temp>cl /EHsc /nologo /W4 /MTd meow.cpp > NUL && meow

Debug

IDL: 2

SCL: 1

HID: 1

C:\Temp>cl /EHsc /nologo /W4 /MDd meow.cpp > NUL && meow

Debug

IDL: 2

SCL: 1

HID: 1

 for me vs2010 IDE is very usefull,Iam very happy for this.

tank you.

Include

#include <boost/bimap.hpp>

#include <boost/bimap/multiset_of.hpp>

#include <boost/bimap/list_of.hpp>

#include <boost/bimap/set_of.hpp>

and watch intellisense crawl to oblivion.

Ah, finally (after 25 mins), it finished. I almost wanted to turn it off completely. It seems one can't get enough of speed :)

Hi Nerijus,

What version of Boost headers were you using?  We tried 1.40 and they work fine, but since Beta2 we did fix lots of issues around intellisense parsing throughput.  This is a kind of bug that we cannot allow in our final product, so let's figure out a way to get us see the same issue you're seeing.  Feel free to send me mail, (batul at microsoft dot  com).

Thanks,

Ulzii Luvsanbat

Windows C++ Team