I already found that one :P
That is also true

thanks.
But i found this:
I really don't like that site for 5 reasons:
None of the code checks for return values, which is the single most important thing you can do when learning DirectX programming. If something doesn't quite work, you're not going to get any sort of indication it's failed until you get a crash - which is likely going to confuse beginners.
There's no code for checking device capability - it all assumes that the graphics card can do 32-bit mode with a (ISTR) 24-bit Z-buffer. I can understand not showing the whole process of testing the card for supported formats since it can be quite a large job and would likely just confuse newcomers, but I think that not mentioning that you really have to check for this sort of thing is a bad idea.
Some of the Win32 code there is a bit dodgey (A busy while() loop to force the game to 40 FPS, only processing a single window message per frame instead of all pending ones, not using AdjustWindowRect(), etc).
There seems to be quite a lot of people starting DirectX who come to the For Beginners or DirectX and XNA forums with crashes or other bugs, and it turns out that their code is based on code from
directxtutorial.com and the problem and associated forum post is a direct result of the bad code from that website - two examples being someone who wasn't checking any return values, CreateDevice() failed and then the game crashed when the device was used, and someone who was trying to do picking (Pointing at an object with the mouse and having the game know you're pointing at it), and was having issues caused by only processing one window message per frame (It felt very laggy), and not using AdjustWindowRect (All the pick coordinates were slightly off).
Some tutorials require a premium membership - and it's really not worth (Again, in my opinion) paying to see more bad tutorials.