Advertisement

Beginner Tutorial Issue

Started by August 21, 2014 02:04 AM
13 comments, last by MRom 10 years, 5 months ago

My last reply was a hint to right-click 1.11 Quiz 1, press R, and post the screenshot again.

L. Spiro

Yes I know, sorry but I'm currently at work. I won't be home for another 9 hours.

I'll do so as soon as I've the chance, thanks again for the help.

I've occasionally had issues where Rebuild all did not fix this, but deleting the Debug and Release directories worked (if they don't exist they are recreated by a build).

I'll try this as soon as I can and let you know the result.

I googled your problem and found a thread with possible solutions so here they are:

I am using Visual Studio 2010.

This happened to me when I installed .NET 4.5. Uninstall of .NET 4.5 and install of .NET 4.0 helped me and error messages disappeared.

Had to install VS 2010 SP1 in order to get it to work again for myself. Lame microsoft.

Do you have Visual Studio 2012 installed as well? If so, 2012 stomps your 2010 IDE, possibly because of compatibility issues with .NET 4.5 and .NET 4.0.

See http://social.msdn.microsoft.com/Forums/da-DK/vssetup/thread/d10adba0-e082-494a-bb16-2bfc039faa80

I had this issue and I solved it with this thread

disable incremental linking, by going to

Project Properties
-> Configuration Properties
-> Linker (General)
-> Enable Incremental Linking -> "No (/INCREMENTAL:NO)"

I'd try installing the Service Pack first. Here the link: click me, please

Advertisement

What Iceey said is bang on. It's a bug, sorta. Actually it's a prior version of Visual Studio being broken by later updates.

His suggestion will fix it, simply run the Visual Studio service pack and you are off to the races.

... welcome to the fun world of C++. ;) Nasty first bug to encounter I will admit.

Just google the error code if you don't know how to fix it. You will often find a solution for it. In this case it is the first result: https://www.google.com/search?q=lnk1123

Sorry, forgot to update. I've been real busy as of late.

You guys were 100% correct, my 'Visual Studio' was out of date and it was a bug with the software, not my program. As soon as I updated it, it worked just fine. I've upgraded to Visual Studio 2013 to HOPEFULLY avoid these issues down the road.

A little fustrating but I'm a little relieved as well.

Thanks again to everyone who took the time to reply, it was greatly appreciated.

This topic is closed to new replies.

Advertisement