It’s also available in Visual Studio’s Extension Manager. Just browse for “Acumatica” and you’ll see it.

In the Acumatica Dev Community Discord there’s skepticism about how useful it will be and listing some items that must be compiled and so could not benefit from this extension. The Forum admin wrote that he thought it can be “a nice speed up for small customizations until Acumatica switches to modern .Net and everyone can use the Hot Reload feature.”

In 2025 A.I. was like an intern coding. This year it’s like a junior dev. It’s truly getting better, and saves a lot of time. But it still needs a human in the loop. This video answers the question, “But why?” well. Perhaps next month that will all change. Things are moving fast…. real fast.

I don’t trust X links to show you anything at all, so here’s my copy/posts from @Scobelizer and @adigyang, titled “When Your Life’s Work Becomes Free and Abundant”. You can go on X to find the original publications, and I encourage that. I save this for myself and wish to share with you. IMHO, we are in the dawning of a revolution that dwarfs the Industrial Revolution and turbo-charges the Information Age. Here’s what @Scobelizer wrote:

——————————————————————————————————-

The post by @adityaag below is a must read.
He talks about his roles as a technology leader in Silicon Valley and how everything he knows has changed in the past few weeks.
“We are in the middle of what may be the largest shift ever in how knowledge work gets done.”
From my perch in Silicon Valley. I see this not as just builders, but marked by curiosity and not resistance. Those who are curious about new things and curious enough to try get the new world. Those that argue the new world is evil do not.
I made lists of 8,200 AI companies here on X. And 35,000 in AI. A small group dove right in. Most ignore it. Even after it slaps them in the face.
I have seen this happen quite a few times in my career.
Most resist and refuse to learn new things.
Would rather just try to do the same thing they did yesterday.
But then a new group comes along and gets the old group fired. That is about to happen in a way that I never have seen before. But I have seen disruption and caused it even.
At Microsoft I was the first to do video interviews with a hand held camera.
My videos got audience while those that had “skills” and “credentials” didn’t. Even with millions of dollars in TV studio equipment.
An executive told me they laid off many who worked in the TV studio after I showed them a new way.
The same will happen here.
But at a much bigger scale.
And in many industries at the same time.
Lawyers. Hollywood. Software. Politics. Journalists. Education.
So many jobs are about to radically change. If not all of them eventually.
But I am preaching to the choir.
If you are reading me you are already curious about AI. Or the algorithm showed me to you because you are angry about AI.
I built my lists for the curious. Almost no one uses them. They are the best on any service of the people and companies building the new world. By far.
In the next week I will show you what I built with them. The curious will eat it up.
The rest will stick their heads in the sand.
The sand people will fall further and further behind every day until it will be almost impossible.
Do I feel sorry for them?
No. It is time to change. There won’t be any apologies. My lists are here for the curious: https://x.com/scobleizer/lists
The others just won’t be relevant to the new world until they change.
The world is brutal that way.
I wasn’t popular with the folks who worked in the TV studio at Microsoft either.
They refused to change. And yes I tried.
Same advice now. Either you get new skills and become part of the new world or you will really struggle. Because people who get it are about to change EVERY PART OF HUMAN LIFE.
The time for grieving and excuses is over.
Either get curious and start to build or someone else will and you will find yourself locked out of the modern world.
Sorry to be so rude. You can blame the messenger. But if you think I am an asshole for saying all this then that is a major signal that you don’t get it and aren’t positioned well to be successful in this new world.
I will spend my efforts helping those that do.
In my first book Shel Israel and I said the same. Either you get into social media, we wrote, 20 years ago, or you will find your career soon will end. We were right. Many lost their jobs, replaced by those who dive right in.
I feel even more strongly that the same is happening now.

——————————————————————————————————-

And here’s what Aditya Argwal (@adityaag) wrote:
——————————————————————————————————-

Not long ago, I spent a weekend writing code with Claude, Anthropic’s AI assistant. I’ve been programming for more than 20 years. I was one of the first engineers at Facebook, where I built the original search engine. I went on to become chief technology officer of Dropbox, where I scaled the engineering team from 25 people to a thousand. Code has been the foundation of my career, the craft I’ve spent my adult life mastering. And after that weekend, one thing was very clear to me: We will never write code by hand again. Something I was very good at is now free and abundant.

While I was building software with AI, I also noticed that the AI agents elsewhere were building social networks, the very product I helped create at Facebook. Little coding agents were spinning up

functional social platforms

for themselves. It’s all a bit silly, but what they produce is kind of indistinguishable from what humans built on the larger internet. Both the form and the function of my early career are now being produced by machines.

I sat with that for a while, and what I felt was wonder mixed with a profound sadness. There’s something deeply disorienting about watching the pillars of your professional identity, what you built and how you built it, get reproduced in a weekend by a tool that doesn’t need to eat or sleep.

But here’s the thing about disorientation: It passes. And what replaced my sadness was something I didn’t expect: a kind of wild, almost reckless energy.

In the five days after that weekend, I produced more code than I had in the previous five years. That is not an exaggeration. The software I was making was better than the code I had produced on my own in the past, and far more ambitious. Things I would never have attempted before, because the cost of building them would have been too high, suddenly became possible in an afternoon. I wasn’t watching myself become obsolete. I was watching the constraints I’d accepted my whole career dissolve.

That shift, from sadness to mastery, reveals something important about this moment. The conversation around AI and work has calcified into two camps. The doomers say we’re all going to be replaced, and the boosters say everything will be fine. Neither camp captures what it actually feels like to live through this. The truth is messier. You can hold wonder and grief in the same hand, mourn a version of yourself while sprinting toward a new one.

What I’ve found more interesting than my own experience, though, is what I’ve observed in the people around me. I run South Park Commons, a community and venture capital fund for builders who are figuring out what to work on next. Through SPC, I see hundreds of engineers, founders and technologists navigating this shift in real time. And there’s a pattern that keeps surfacing: The old playbook for evaluating talent is breaking down.

One of our members recently ran about 20 work trials for engineering hires—essentially, extended, weeklong job interviews—and found zero correlation between years of experience and adaptability to AI tools. Another member told me that what predicted success in hiring people who possess that adaptability was evidence of a builder’s disposition: cool personal websites, side projects, an obvious love of making things. FAANG on the résumé and a name-brand university, meanwhile, predicted almost nothing.

A third member shared something even more striking. His company started giving tasks that were intentionally too long to complete by hand during coding interviews. The assignment became a remarkably clean filter: You could quickly tell who was using AI tools in their daily work versus who had merely been reading about them. The gap in the number of lines of code the two groups write wasn’t 10%. It was closer to 10x.

This might sound like a narrow observation about the software industry, but I think it’s something bigger. We are in the middle of what may be the largest shift ever in how knowledge work gets done. And the trait that matters most isn’t intelligence, or credentials or years of experience. It’s someone’s relationship with change—not whether they’ve seen change before, but whether they run toward it.

There’s a common assumption that younger workers will adapt more easily and older ones will resist. But the dividing line isn’t generational—it’s dispositional. Willingness to change seems to operate as an independent variable, cutting across age and seniority in ways that defy easy categorization. I’ve watched 15-year industry veterans pick up these tools and absolutely crush it, while some recent graduates treat AI as an abstraction to be debated rather than a tool to be used.

As an investor, this realization has reshaped what I look for in founders. The people I’m most excited about aren’t the ones with perfect pedigrees. They’re the people who seem constitutionally unable to stop tinkering, who get antsy when things stay the same, who treat every new tool like a puzzle they need to solve before the day is over. I’ve started to think of it as the difference between your résumé and your restlessness. I’d bet on restlessness every time.

Silicon Valley has always been one of the most meritocratic industries, but that has never meant credentials and experience don’t matter here. They just matter less. Now they are going to become even less important.

Paul Ford wrote beautifully in The New York Times about

vibe coding’s potential

to democratize software, to put the power of building into more hands. I share his optimism. But I’d add that this democratization isn’t just about access to tools. It’s a reordering of what we value in people. We spent decades building a culture that worships credentials and experience. Those things aren’t worthless, but they’re no longer sufficient. The new currency is adaptability, and unlike a Stanford degree, it’s available to everyone.

If anything, this shift is teaching me what it is like to be human again—not human in the romantic, AI-can-never-replace-us sense, but human in the uncomfortable sense, the part where you have to let go of the thing you were in order to become the thing you might be.

That’s always been the hardest part, long before AI. The technology just made it impossible to ignore.

Version 2022.9 or higher is required because Visual Studio became a 64-bit application with VS 2022. That broke the Windows Forms designer until the team created a 32-bit out-of process designer. Version 2022.9 had that and was released on Feb. 29, 2024. If you have the latest VS 2022 version installed, this project template will work.

You need to enable this under Tools > Options > All Settings > Preview Features.

When you install the extension, all the controls for the Dynamics SL SDK will be included in the toolbox, as shown below. You will need to enable the out-of-process designer when asked. In the past, it was necessary to run two “vsix” projects to have the full SDK project, including the toolbox controls.

As of Nov. 21, 2025, the extension is in preview. Please provide any feedback in the comments for this post. When it’s no longer in preview this paragraph will be removed and any changes from the initial preview release will be noted here instead.

SteadyCode continues to support customers who are running Dynamics SL, and work has increased as customers integrate with other systems while preparing to move the financial and other modules to other ERP solutions.

If everything else seems to be correct it’s sometimes helpful to export all the other customizations on that form with VBA as text. Save, then import your new customization, then re-import the others you just saved. I’ve seen that work several times.

The only way to detect this is specifically ask about the password he or she uses to login. The password will work to login to other things, like Office 365 or a Windows workstation.

As of March, 2023, you cannot use the Dynamics SL 2018 CU9 SDK or prior versions with the Visual Studio 2022 Windows Forms designer. The solution is to use Visual Studio 2019 or earlier versions.

The reason is that VS 2022 is a 64-bit application and the Windows Forms designer requires 64-bit controls. The Dynamics SL SDK controls are 32-bit controls. You cannot add them to the toolbox and the designer will show nothing but an error message if you open an existing project. You will not be able to use it. 

Here is a link to the thread of developers complaining about this and the VS Windows Forms team responding. In short, they worked hard to make the designer work with .Net Core, and in the process broke x86 .Net Framework apps. You can scroll to the bottom to see the latest workaround suggestions. If you were interested enough to read this, please click the link and vote the issue up.

It is possible to recompile your SL SDK project in VS 2022, without making any changes to the designer, but it gets annoying very quickly when you can’t make any design changes.

2023-05-04: Blogger Grant Winney also wrote about this issue with a detailed description on how to recreate it.

2023-08-31: There were several new updates to the thread above at the end of August, 2023, indicating that a 32-bit out-of-process editor for the WinForms designer will ship with Visual Studio 17.8. It would be great to use Visual Studio 2022 to develop Microsoft Dynamics SL solutions, like it was with all earlier versions!!!

2023-10-20: The current preview version of Visual Studio 2022 (17.8.0) contains an out-of-process designer for the .Net Framework which you must enable under Tools > Manage Preview Features. It will let you view and reposition SL SDK controls on projects created with earlier versions of Visual Studio (pre-version 2022). At this time it is not possible to add the Microsoft.Dynamics.SL.Controls.dll to the toolbox, so you cannot add new controls to a form. I have submitted a bug report to the Visual Studio team, and hopefully they will fix this before VS 17.9 is released.

2025-11-17: Microsoft fixed this in version 17.9, as they announced on Leap Day, 2024. It’s wonderful to be able to use the current version of Visual Studio for Dynamics SL development again!!! They also published a troubleshooting article with more details. Wish I’d noticed this sooner.

NEVER check Tools > Options > Code Settings > Require Variable Declaration in the SL Customization Manager VB Editor. That will add “Option Explicit” to the top of all your files. While that may help in the files you wrote, it will also add it (again) to the top of the VBTools_VBA module. You won’t probably think to look there. There is already an “Option Explicit” underneath the comment containing the copyright, etc. from Microsoft Dynamics. Having a new one above that comment may stump you for a while, at least until you think to look in a file you shouldn’t change… or run across this post.

It will also be added when you import a perfectly good customization that works in other environments, such as production.

It works! I created two labels on the second form to show the command line arguments passed by the first. I called ApplGetParms() twice on the second form to get each of them. That emulates what a standard SL SDK app would do to retrieve them. The second exe was named “STOBJ01”.

Here’s the code. The first line was at the form level. The rest was in the button handler.

Private WithEvents _sivApp As SIVApplication
…
Dim parmStr As String = PRMSEP & “2000” & PRMSEP & “Second_Param”
Dim sivErr As Integer
Dim osErr As Long
_sivApp = StartAppAndAutomate(exePath & “STOBJ01.exe ” & parmStr, sivErr, osErr)

Note the space after “.exe” within StartAppAndAutomate. It didn’t work without that. Using the constant PRMSEP here is optional with just one argument, but is required with multiple args.