Author Topic: Hows the migration going?  (Read 892 times)

0 Members and 1 Guest are viewing this topic.

It's Alive!

  • Retired
  • Needs a day job
  • Posts: 8926
  • AKA Daniel
Hows the migration going?
« on: February 03, 2024, 07:10:45 PM »
I only have one C# project out there in the wild.
Thinking about porting it to C++. Have you tried any COM components?

kdub_nz

  • Mesozoic keyThumper
  • SuperMod
  • Water Moccasin
  • Posts: 2165
  • class keyThumper<T>:ILazy<T>
Re: Hows the migration going?
« Reply #1 on: February 03, 2024, 07:12:22 PM »
Nope ;-)
Called Kerry in my other life
Retired; but they dragged me back in !

I live at UTC + 13.00

---
some people complain about loading the dishwasher.
Sometimes the question is more important than the answer.

It's Alive!

  • Retired
  • Needs a day job
  • Posts: 8926
  • AKA Daniel
Re: Hows the migration going?
« Reply #2 on: February 03, 2024, 08:46:07 PM »
I have an etransmit events watcher written C# and COM. I hate COM in C++ so I wrote it in C#.
Guess I should try porting first

kdub_nz

  • Mesozoic keyThumper
  • SuperMod
  • Water Moccasin
  • Posts: 2165
  • class keyThumper<T>:ILazy<T>
Re: Hows the migration going?
« Reply #3 on: February 03, 2024, 09:20:15 PM »
I've been warned that if I continue to critisize  [indicate the faults of (someone or something) in a disapproving way.] VB in public I'll get a severe talking to.

I assume the same applies for COM.

though the dynamic keyword in C# makes it a little easier.

Will be interesting how it handles nullable values   :|
Called Kerry in my other life
Retired; but they dragged me back in !

I live at UTC + 13.00

---
some people complain about loading the dishwasher.
Sometimes the question is more important than the answer.

It's Alive!

  • Retired
  • Needs a day job
  • Posts: 8926
  • AKA Daniel
Re: Hows the migration going?
« Reply #4 on: February 03, 2024, 11:14:25 PM »
IKR, unfortunately I use TransmittalAddFileNotificationHandler, which is ActiveX only
Pretty painless though,  I had to manually add these to prevent VS adding subfolders to the output path.

<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
<AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>