Odd things in Visual Studio 2013

[LPeter1997]

Hi!
I've successfully installed SFML with VS2013 (with a template). It works, the provided tutorial code works perfectly. But... in the editor I get a lot of red underlines, like it's a mistake. Another thing is I get 12 errors in the error list if I run the  program. For example the first one: Cannot open source file "SFML/Graphics.hpp".
Lastly, in the Output panel I get a lot of these:
'SFML2 Application1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Cannot find or open the PDB file.
'SFML2 Application1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.

I don't think it's normal. Could anyone help fixing these?

Oh, before I forget, I used this guide:

Could I get some help installing this?

In order to make things easier, I took a shot at doing a bundle (VS2013 binaries + template) that is simpler to install and use. Here are the steps:

BINARIES
1) Download the binaries from here.
2) Unzip anywhere you want. As a suggestion, you could use C:\SFML-2.1.
3) Create a system environment variable called SFML2_HOME pointing to the folder where you unzipped the file.

TEMPLATE
1) Download the binaries from here.
2) Copy the attached ZIP file to Documents\Visual Studio 2013\Templates\ProjectTemplates under your home folder.
3) Open Visual Studio and click FILE, New Project... The "SFML2 Application" Visual C++ template is now available. Create your project.
4) The project is all set up, and the small bundled sample program (the one from the tutorial) is ready to compile.

Details:
The binaries and the template were made with Visual Studio 2013 Express Edition Update 1 running on Windows 8.1 Pro x64. Since VS2013EE only ships with a x86 SDK, I couldn't try and make the template x64-compatible. I also didn't bother building static libraries.
Also, it doesn't matter if you have the SFML2 DLLs in your PATH environment variable nor in the output folder. The template includes a Post-Build Event that copies the DLLs from $SFML2_HOME\bin to the output folder in case they're not there already.

[zsbzsb]

This is why those templates are not recommended. Programmers should learn to setup their own tools instead of relying on premade templates.

What you should do is compile SFML yourself as there has been many important fixes for SFML since 2.1 was released. Secondly follow the official tutorial to setup your project.

Lastly, in the Output panel I get a lot of these:
'SFML2 Application1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Cannot find or open the PDB file.
'SFML2 Application1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.

You can very safely ignore these warnings.

[Laurent]

What you should do is compile SFML yourself as there has been many important fixes for SFML since 2.1 was released.

... and as there's no precompiled version of SFML for Visual Studio 2013.

[zsbzsb]

... and as there's no precompiled version of SFML for Visual Studio 2013.

Unless you pick the binaries from those template threads 

[LPeter1997]

Really? There is no just a simple template to set up the project? Always have to do the same again if I want to create a new project? That's disappointing... 

There's no offical download for VS 2013... now what?

[Laurent]

Templates are for beginners or fast prototyping. Once you know how to setup a library -- 30 seconds max -- you just do it. It's not a big deal compared to the weeks / months / years you'll then spend on the project

[zsbzsb]

There's no offical download for VS 2013... now what?

Build it yourself, it takes all of maybe 15 minutes if you follow the tutorial. Or if you want, you could get a nightly build here.

[LPeter1997]

You guys are right. I'm just too picky sometimes