billroper | Entries tagged with c#

I have been fixing a silly number of bugs in the last couple of days.

One of the bugs that I am fixing right now is one that I thought was going to be a horrible amount of work. It turns out that I can fix it rather simply, which I found out after digging through the code.

I just can't *test* the fix, for reasons having to do with Microsoft Excel's lousy handling of COM memory and garbage collection in .NET.

So I am checking in the fix and passing it along to someone who has installed the 32-bit version of Excel, which seems to do a better job of garbage collection than the 64-bit version. That's not what I would have expected, but it is what appears to be true.

Some problems are just annoying.

Crossposts: https://billroper.livejournal.com/1852324.html

I am still crawling through our user-interface code. I have cleaned up a great many things, but there are some interactions that are perplexing me. I think I have some ideas about how to proceed, but I'd like to talk with one of the fellows who wrote it.

I'd like to give it back to him, actually. We'll see how that goes. :)

Crossposts: https://billroper.livejournal.com/1846914.html

I have fixed a great many bugs this week.

Right now, I'm looking at the debris in our Visual Studio 2019 port. The COM handling machinery there seems a bit idiosyncratic, but it's possible to work around those eccentricities once you find them. I'm doing bulk corrections and it seems to be stable.

But I've found some code in our UI layer that I really don't like. I think I can fix it in a day and then we'll see if some of the idiosyncrasies in *our* code will be good enough to go away.

Crossposts: https://billroper.livejournal.com/1846687.html

I am not as sharp at C# as I might like to be. Nevertheless, I have plunged into a C# project which I expect to finish this week where I am making some changes to many of our dialogs. A baker's dozen or so of dialogs by my quick count.

I have hacked and slashed my way through more than half of this now.

We'll see how long it takes to finish it up. I don't think there are any more really difficult ones, but I'll find out when I see how the existing code looks.

Crossposts: https://billroper.livejournal.com/1841015.html

It's time for another round of comparative programming languages, as I have suddenly inherited a chunk of C# code that needs work. Happily, C# and Java have a lot of similarities, except when they don't.

I spent a couple of hours this afternoon and managed to do a moderate amount of cleanup. There's another bigger thing I want to try on Monday -- because I am *not* going to try it this weekend. :)

Crossposts: https://billroper.livejournal.com/1836108.html

So we've been trying to port our code up from Visual Studio 2010 to Visual Studio 2019 for a bit less than two years now. (I started aiming for Visual Studio 2017, but that eventually became an obsolete target.) Most of the code appeared to be working, but when it was finally tested by our QE team, an intractable bug popped up.

The intractable bug has been sitting there for some obscene length of time. In the last two days, we have spent four hours on a session with the other group in our company that is trying to talk to our code across COM in order to make this work. Today's session didn't manage to solve the problem either.

About ten minutes after the session ended, I went to my machine and fixed the problem by setting one switch in the compile.

My Google-fu is strong, but it really helps when you finally find out what is going wrong in the communications protocols.

*sigh*

We'll see if this fix sticks...

Crossposts: https://billroper.livejournal.com/1835976.html

I finished up the C# port today and checked it in.

Then I went and bothered one of my colleagues to show me how to use something that he'd mentioned in Java. After a bit of work using Jackson annotations, one of my Java classes is now happily emitting Json that the UI team should (with a bit of luck) be able to consume.

Well, that's the theory anyway.

Crossposts: https://billroper.livejournal.com/1791859.html

For someone who doesn't actually know C#, the port of this chunk of my code from Java to C# is going quite well. I think that I'm likely to finish the whole thing up tomorrow unless something goes horribly wrong.

The biggest chunk of time was spent sorting out the differences between a Java iterator and a C# IEnumerable interface. Other than that and a few scoping issues, things are going pretty well.

We'll see what happens next. :)

Crossposts: https://billroper.livejournal.com/1791449.html

Someday, I will get around to writing "A Pirate Looks at Fortran". In the meantime, I am looking at C#, because I think that the easiest way to get some things working in our C# user interface will be to port cut-down versions of my Java code over to C# so that the simple data is resident in the same process as the UI.

Today, I ported one of my ID classes and the ID caching class from Java to C#. Only the names of all the damnable methods have been changed as I move from one language to another (not *my* methods; the ones in the libraries). But it looks like it should work.

Crossposts: https://billroper.livejournal.com/1791187.html

Bill Roper's Journal

Entries tagged with c#

The Fix Is In

(Inter)Face the Music

Fixing the Bugs

Plugging Away

Comparative Programming Languages

Intractable Problems Solved Cheap

There's a Friday the 13th Joke Here Somewhere...

C# Dressed Man

A Pirate Looks at C#

Profile

May 2025

Syndicate

Most Popular Tags

Page Summary

Active Entries

Style Credit

Expand Cut Tags