Actually, it means you're impatient
.
Standard C++ in is almost a superset of standard C. That basically means that almost any standard C program will also be a valid standard C++ program. So in that regard, it will help you immensely. There is a lot of C++ syntax that is not valid C, basically all the OOP stuff, exceptions, namespaces, etc. However, almost any C program you see is technically also a valid C++ program, even if it doesn't use classes, exceptions, etc. Thus, if you can read any C++ program, you should be able to read any C program.
The whole .net thing, however, is specific to MS stuff. Also, MS doesn't really support C any more. Yes, their VC++ compiler will compile C programs, but they have made no real effort to keep up with the changes in the C language since the 1990s, so basically .net and C don't go together so much. Certainly, if you program C for embedded devices, Linux, or anything non-MS, then .net is useless. But C++ itself is still very useful.
What it all boils down to is this:
Hypothetically, you learned how to program in college, not simply to use C++.net. The tools were C++ and .net, but that's largely irrelevant. What's most important, is whether you learned to solve problems algorithmically, and whether you really learned the core concepts of programming and computer science that makes language transition easy. If you have those two things, then there should be minimal difficulty in picking up C. Even if you just have the former, it should be easy. Basically, it will boil down to learning the standard C libraries, and learning what syntax is only valid in C++ (remember most C syntax is valid C++, so you know the syntax). That being said, there may be a few tough hurdles, and it will be a bit difficult to break your first-language "bias", and habits of thinking in C++.net, but it's not really that hard.