VS 2013 Those pits after getting started

In order to experience more new C + + features, keep up with the times, installed VS2013 as a demo development tool.

At this stage is only the VS2013 local characteristics of contact, here just write down some personal experience

Every software will inevitably have some bugs or design less friendly places, VS2013 is no exception

VS2013 used after the pit left:

1 class method declaration syntax detection strict loosening

In VS2008, once a class declares a method, it must implement the method, or the compiler will make an error, but in VS2013, the rule does not seem to apply. This means that after a method declaration, it can be compiled even if it is no longer declared.

Although this low-level error is seldom committed, VS2008 is very detrimental to the backward-compatible VS2010 of the code. And in the case of calls to the dynamic link library, the compiler will directly error, the cause of the error is other, for debugging, it is really a waste of time, this is the author was VS2013 after the bad, sometimes make mistakes. This is a bad habit.

2 VS2013 not (direct) support for XP systems

Microsoft in order to encourage more users from the XP platform upgrade, VS2013 started not directly support XP system, that is, directly with the VS2013 development program, can not be run on XP, of course, through some configuration of the project itself, the software can resume support, But in a way it's more of a configuration problem.

3 third-party libraries have insufficient support for the latest version of the IDE

VS2013 is also a new product, the penetration rate is not so high, for some libraries that rely on the IDE, such as the POCO library some classes will temporarily not support the VS2013 call, but can run normally in (VS2008, VS2010), this is a very pit place. Students who rely heavily on third-party libraries need to be cautious about choosing a new IDE

4 Those pits of the auxiliary plug-in

with the transformation of Microsoft to services, VS2013 's support for plugins seems to have made significant changes to the architecture, VS2013 provides services to install plug-ins online (the installation is very pit, the number of plug-in shops is poor) and many plugins are not provided VS2013 Support or charge (VISUALSVN client version plugin). To upgrade from the 2010 version, there are still some uncomfortable, and not accustomed to.

Summary:

Upgrading is always good, but learning always takes a time cost.

Consider upgrading to VS2013 students, it is recommended not directly into the work of use, to a certain extent, will affect the efficiency.

The author's approach is:

When developing the demo, use VS2013 directly, the official commercial version or use the familiar IDE before, so as not to introduce some unnecessary trouble because of the development tool, but also can use the vs2013 quickly.

VS 2013 Those pits after getting started