A little over a year ago, I asked for feedback on Code Review for a unit testing framework I created in VBA. Development of this project has been off and on for the past year. Sometimes I wouldn't touch the project for months. Other times, I'd be working very intensely on pushing updates. The pro...
@MathieuGuindon, when the day comes that RD2 is deprecated and RD3 is the main project then you could move RD2 to it's own branch. Then merge in the entire RD3 codebase into the main RD repo using --allow-unrelated-histories. It's not pretty but it would allow you to have this obvious shift in the history where 3 comes in.
I'll try to deploy the test site over lunch. The hour, not the protocol. It's deploying over stupid-basic ftp like it's 1997.
db schema is updated, ...I should probably script my local data and migrate it over
Side note, I didn't make a test schema, so it's not really a test environment: the old site reads from the dbo schema, new site reads from/writes to a v2 schema - so it's more like a pre-prod environment where we can seed the v2 site and test the front-end and see if anything needs tuning before I overwrite the old site.
Another side note, in RD3 I changed the VersionCheck service to query the API, so it's getting not just a version string but the exact same json response from the endpoint above, so it's the same url to get both main and next tags now
Yeah. ..but then the API client could also serve any FeatureItem content, ...we could render inspection/quickfix/annotation examples in-app if we wanted
if you want to publish MVC project to GoDaddy shared windows hosting, this is the answer. GoDaddy does not run executables like csc.exe — Jeson MartajayaDec 12, 2019 at 23:23
fml
I do recall nixing the compiler stuff in the old site's web.config, but the closest I got with this one was an error about $ being unexpected in a string interpolation on the home page code-behind
I've already retargeted down from .net 6 to Framework 4.8, this is ridiculous
oh
oh no
on no no no no no
> Microsoft .NET Framework Version:**4.0.30319**; ASP.NET Version:**4.8**.9037.0
(that's why there are no feature items yet, ...the feature details pages shouldn't be blowing up like that though)
weird that I'm getting an error page from postman hitting the API with a PUSH, when the test site is hitting the API with many GET requests without any issues
there's a glitch with the xmldoc update service, it throws some key constraint violation exception when records already exist... that's pretty much next on my plate
(after I push the local data!)
lol the "edit feature" modal is too tall for my laptop, the buttons don't show up :facepalm:
lol the download links should probably be disabled on mobile, be it only because the dropdown panel overflows to the right... Actually downloads should be disabled whenever the client isn't on Windows
Dammit I'm finding all sorts of things that aren't working
VBA Rubberducking
VBA Rubberducking