v1 <- CodeProject[^] M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

v1 - CodeProject[^] M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

Spammer terminated. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Some of us agree.

I explained what you should do to correct this in my previous reply. Passing a class pointer or reference is just the same as passing any other type. So a simple example: // a useless class class Foo { private : int bar; public: Foo(int i) : bar(i) {} // constructor takes a value int getBar() {return bar; } // this method returns the value }; // an arbitrary function which accepts a Foo* int MyFunc(Foo* param) { int rc = param->getBar(); // ask the class object for the value return rc * 2; // and return it doubled } int main { Foo* pFoo = new Foo(4); // create a new object with a value of 4 int ans = MyFunc(pFoo); // call MyFunc passing it the pointer to the class object cout << "result: " << ans << endl; return 0; } And all of that, and more, is fully explained in any C++ reference, either online or in printed copy.

I have a general gripe with Visual Studio where you need a separate project per main(). I tend to code each entry point as a separate class in a DLL project with a myMain(). I have one Console app that just calls into the correct class. This also allows you to UnitTest the separate classes.

I think it only costs about $3k/pound to put something on a Falcon 9. I couldn't afford a very heavy satellite, but it's pretty interesting to google that and realize I almost definitely could get some little something up there. Barring all the stuff like they probably don't just let anyone chuck a bit onto a rocket to fling into space and there's almost definitely more bureaucracy to it than just paying. Edit: The CodeProject Payload Project? That would rock. If y'all do it, I'd definitely want to try to be some part of it.

In your InitializeWebViewAsync method, try creating a CoreWebView2Environment object (you'll need to give it a folder path to use) and passing that to the EnsureCoreWebView2Async method. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

"Despite the hype surrounding Microsoft's lead in this category, what's often less talked about is how much further ahead Microsoft would be if Satya Nadella and the team at Microsoft hadn't made a range of baffling, short-sighted decisions in previous years." I blame AAPL. No, truly, I do. Not that MSFT isn't blameless but it's relative moralistic bar lowering in the name of the buck and once AAPL dropped the bar to the center of the earth... It's "oh crap, we need to be a bit more evil or we'll be financially smoked in the charts". It's not just MSFT they collaterally damaged like this with their wanton greed.

I would hate this. It would probably be good for me. I lean heavy on the whole fast build and see if it goes and correct what doesn't. I'm sure some could watch a recording and think it spaghetti chucking. Intellisense has gotten progressively worse with the verbosity of its descriptions because of the brigade against all code comments (maybe especially the XML ones). So you get method definitions from nugets where even if it's clear how you should call something, exactly what's going to happen when you do is a scientific endeavor of experimentation. Maybe it's exactly spaghetti chucking, but what other way is there to decode these black boxes?