-
March 12th, 2015, 07:46 AM
#1
Vs2005 -> vs2013
From Past 10years we were working on VS2005 VC++ and currently shifted to VS2013.
I dont know from where to start as there are many classes added with new features.
Unable to find good books/sites aswell on VS2013 VC++ which covers from basics to advanced programming.
-
March 12th, 2015, 07:53 AM
#2
-
March 12th, 2015, 08:15 AM
#3
Re: Vs2005 -> vs2013
you should start getting your old code to WORK first.
There have been quite a few breaking changes since VS2005.
tip: enable warning level 4, and FIX all the warnings properly.
-
March 12th, 2015, 08:16 AM
#4
Re: Vs2005 -> vs2013
Originally Posted by brraj
I dont know from where to start as there are many classes added with new features.
Perhaps, you will read the documentation about "classes added with new features" in MSDN?
Victor Nijegorodov
-
March 12th, 2015, 08:49 AM
#5
Re: Vs2005 -> vs2013
MS VS2013 implements c++11 (with a few exceptions ). So rather than trying to find good books/sites for MS VS2013, I would suggest you investigate resources for c++11.
As you have found, c++11 has many changes from c++98 (MS VS 2005). As someone who has recently been involved with converting from earlier versions of VS to VS2013, please heed what OReubens says in post #3. You may be tempted to start using these new c++11 features in your code as part of the conversion exercise. I would strongly advise not to be so tempted. The first step IMO is to get your existing code base to compile cleanly at warning level 4 (or to document every level 4 warning as to why) and then to test your programs to make sure that they work exactly as they did before. Only once that you know your code base is c++11 compliant would I then consider how usage of the new c++11 features might be applied to your code.
AFAIK there is not much resource available that teaches c++11 assuming you already know c++98/03. perhaps one of the best books is
Professional c++ 3rd edition.
http://www.amazon.co.uk/Professional...sional+c%2B%2B
There is also The c++11 Programming Language 4th Edition - but this is a reference not a tutorial
http://www.amazon.co.uk/C-Programmin...2B+programming
You could also be interested in
http://www.cplusplus.com/info/
http://channel9.msdn.com/events/GoingNative/2013
https://isocpp.org/wiki/faq
All advice is offered in good faith only. All my code is tested (unless stated explicitly otherwise) with the latest version of Microsoft Visual Studio (using the supported features of the latest standard) and is offered as examples only - not as production quality. I cannot offer advice regarding any other c/c++ compiler/IDE or incompatibilities with VS. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/ and can be used without reference or acknowledgement. Also note that I only provide advice and guidance via the forums - and not via private messages!
C++23 Compiler: Microsoft VS2022 (17.6.5)
-
March 13th, 2015, 02:13 AM
#6
Re: Vs2005 -> vs2013
Thanks all for the reply.
Originally Posted by OReubens
you should start getting your old code to WORK first.
tip: enable warning level 4, and FIX all the warnings properly.
Done. Its working fine.
Thanks for the tip as i was able to clear lot of warning and some i have to learn why in the first place warning is displayed for.
@VictorN - I did a msdn search for the same it displayed VS 2010 features
https://msdn.microsoft.com/en-us/mag...ee336130.aspx\
is this fine, nothing major after VS2010 release.
Originally Posted by 2kaud
Thanks for the links
-
March 13th, 2015, 07:11 AM
#7
Re: Vs2005 -> vs2013
I agree with 2kaud and am glad you have followed the advice to "clean up the code"....On the topic of "to document every level 4 warning as to why", I strongly suggest that this be done in the code itself, and then a pragma used to suppress that individual instance of the warning. By doing this you will have ZERO warnings in a compile, which makes it much easier and reliable to catch a new warning as you continue to develop. Situations where "oh, we have 213 warnings, have always had them and know why" are VERY Dangerous.
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009,2010
In theory, there is no difference between theory and practice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first
-
March 13th, 2015, 08:21 AM
#8
Re: Vs2005 -> vs2013
Originally Posted by brraj
Done. Its working fine.
really.... ? That sounds a bit strange to me, since you only had a day to do this.
Either your OP was a bit excessive with the "many classes", and your entire code base is very small or you have some "unusual" type of program that has avoided all the issues somehow.
it took us over a week with a handfull of devs to get our codebase (4million lines of C++) converted.
at low 'C' level :
- there's the whole 'secure string' library issue to deal with (change str...() functions like strcpy() etc to strcpy_s())
- the entire change to posix functions (both interface and behaviour changes)
- atoi(), atol(), itoa(), ltoa() functional changes
- whole ranges of functions that have become deprecated (i.e. removed from the standard and supported as a implementation specific _ prefixed version only).
At c++ level
several containers and iterators had interface and behavioral changes.
several classes that have become deprecated
changes to a few regex patterns.
just because your code compiles, doesn't mean it'll WORK properly yet. Did you do regression tests on EVERYTHING ?
-
March 13th, 2015, 08:26 AM
#9
Re: Vs2005 -> vs2013
Originally Posted by OReubens
really.... ? That sounds a bit strange to me, since you only had a day to do this.
Either your OP was a bit excessive with the "many classes", and your entire code base is very small or you have some "unusual" type of program that has avoided all the issues somehow.
I don't find it surprising based on the way I read it... The "many classes" could easily refer to all of the changes in the "language/libraries", few of which may actually be used in the program(s) in question. I have also seen many situations where the total LOC is under 10K. So you accomplishing your task in a week could easily be done by a single person in a day for that side codebase....
I do agree 100% with "just because your code compiles, doesn't mean it'll WORK properly yet. Did you do regression tests on EVERYTHING ?"
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009,2010
In theory, there is no difference between theory and practice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first
-
March 13th, 2015, 08:36 AM
#10
Re: Vs2005 -> vs2013
Originally Posted by OReubens
...
it took us over a week with a handfull of devs to get our codebase (4million lines of C++) converted.
at low 'C' level :
- there's the whole 'secure string' library issue to deal with (change str...() functions like strcpy() etc to strcpy_s())
...
You seemed to convert your codebase from some older than VS2005 version.
All these Secure CRT Functions were implemented in VS2005.
Victor Nijegorodov
-
March 14th, 2015, 05:38 AM
#11
Re: Vs2005 -> vs2013
Originally Posted by VictorN
You seemed to convert your codebase from some older than VS2005 version.
All these Secure CRT Functions were implemented in VS2005.
Hmm you appear right on that, it was the vs2003 conversion that took us that long.
-
March 14th, 2015, 09:03 AM
#12
Re: Vs2005 -> vs2013
Originally Posted by OReubens
Hmm you appear right on that, it was the vs2003 conversion that took us that long.
Yeah! And in my case about_two_week VC+S2010 conversions occured...
Victor Nijegorodov
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|