Support Board
Date/Time: Mon, 21 Apr 2025 18:34:20 +0000
Post From: How to Use Visual Studio 2022 Community to Develop Custom Studies for Sierra Chart
| [2025-02-23 15:07:07] |
| Deiter - Posts: 13 |
|
@User384728, that was a great addition to this! This was something that puzzled me when I worked through this process yesterday. I did the brute-force thing and copied all the .h files from D:\SierraChart\ACS_Source so that all the #include statements would work--but I knew that was a clunky, vulnerable way to do this and needed something better. You beat me to it, and it works great! Thank you. @ondafringe, THANK YOU for putting this guide together. I am very happily running this workflow through VS2022 and it works brilliantly. My [KEY LEARNING] in the process thus far: - handling of header files, as @User384728 already graciously pointed out. - it's absolutely vital to remember there are often different settings in VS2022 for DEBUG versus RELEASE (as both of you have highlighted). This tripped me up several times in the process of setting up VS2022 last night--but that was my fault for doing this late at night after a long day and another aspect of being very, very new to using Visual Studio. - Powershell. Oh Powershell. I have been a Microsoft guy since making the jump from the TRS-80s in my elementary school's computer lab way back in 1985 (we were sooooo very fortunate to have such a facility and dedicated teacher in a tiny town in Michigan way back then). I have never been a computer person as my primary job (programmer, sysad, etc.), I just used them as tools in the various things I do, so I have struggled with the increased complexity of operating systems and network technology over the years. Powershell is a prime example. I get that it is powerful. I get that it (or something like it) is needed for complex networks in the modern world--but it just crushes my soul whenever I need to dip into it 'cause I'm not a network admin (other than running my home network) who uses it every day. Your instructions were excellent @ondafringe, I just needed to spend a lot of time learning about and changing ExecutionPolicy settings on my machine to make it work. Big tripping point for me was keeping the various versions of Powershell on my machine straight, and getting VS2022 (and the VS extension "PowerShell Tools for Visual Studio 2022) to use Version 7 of Powershell. - This is a very new addition to my tech workflow - Grok AI via X. This is what saved me with the ExecutionPolicy stuff. I have tried several times over the years to make this stuff work on my machine, but I would get about 10 websites, 20 Substack posts, and 30 blog posts into the journey and just give up. Grok has been surprisingly helpful and has enabled me to handle a couple home network projects that have stumped my for a long time. Thanks again! Date Time Of Last Edit: 2025-02-23 15:09:27
|