icy mccoolname

Personal taste is that I like to draw all my intersections by hand; this city is a nice record of how I've come along what new ideas I've picked up along the way. The 5-way rail interchange (N/S/E/W/Cargo Airport Hub) remains my favourite I've done; even if it feels like an accidental turbine! It's great at keeping things flowing, especially since I like to use non-standard length trains for both pax and freight! The trumpet, stack and parclo are pretty standard, but were the first ones I did. No anarchy or engineering mods for those either, beyond fine-road tools. )b

After getting some pointers on the steam forums, I found that as of Visual Studio 2019, you can't change Framework type through the settings UI. Here's how to setup a new project in Visual Studio 2019 for development of CS Mods: Create a New Project (or take an existing project and skip this step): C# Class Library (language "C#", project type "Library") Project/Solution name and saved location as desired (refer original post) Choose any Target Framework, we'll be changing this in the following steps. Once created, Right click the name of the project in Solution Explorer (eg SecondMod), and select Unload Project This opens the .csproj file for editing. Under <PropertyGroup>, Change <TargetFramework> and add <LangVersion> to match the following: <TargetFramework>net35</TargetFramework> <LangVersion>preview</LangVersion> This gets you off the 'Core' or 'Standard' frameworks and onto the "Framework n.n" frameworks. LangVersion is there to force the program to allow you to use a more current version of C#, which otherwise leads to compilation errors. You may not need LangVersion to compile your code, your mileage will vary on this. Save Right click project ( eg "SecondMod (Unloaded)" in Solution Explorer > Reload Project ) Now if you right click the solution name and select properties, the Target Frameworks should read ".NET Framework 3.5". Other, more recent versions may be available, if you want to use a newer version that should be fine, the point is you can now select these from the UI! From this point, the remainder of the tutorial remains the same (or close enough) in Visual Studio 2019. Hopefully 2022 doesn't change much beyond this! -- This is probably bread and butter .NET, but in my defense the last time I used C#, we were still using Visual Studio 2012!

Heya, does this still work with .NET framework 3.1 or .NET 5.0, using VS 2019? (In other words, how vital is it that one uses .NET Framework 3.5 exactly?) I'm having a strange issue where I follow the instructions (as best I can) for Visual Studio 2019, however the compiled Mod doesn't show the supplied name or description in the Content Manager. Putting the .cs file in the location from the first step works fine("SecondSecondMod" in the image), so I'm wondering if it's the framework I'm using? //Happy to spin this into it's own thread if modern dev setups are a separate topic :"D