Ok, the readability suffers a bit - sorry for the bleeding eyes
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
Identify your primary objective. If it is producing a new application, then stick to the language you know best, but if it is learning C++ then follow Richard's advice.
I faced the same choice some years back, and since my primary objective was learning C++ I went down this route. Had it been the production of a new application I would have continued with COBOL.
I never had any desire to branch out into C# but it made practical sense to adopt it for the WCF and ASP.NET aspects so that got learned too. Nowadays Visual Studio, and particularly the express versions offer better UI experiences in C#, so consider that C++ may not offer all you desire.