Function Syntax: FeatureLinesStyleExtra Version: 1.0 Date: 15.06.2026 13:17:06 Version: 1.1 Date: 15.06.2026 1:58:22PM N/A Description This project is an Autodesk Civil 3D C# .NET plugin that creates Civil 3D feature lines from selected drawing objects. The project recreates the Civil 3D create-feature-lines-from-objects workflow and adds a custom WPF dialog with wildcard feature line style filtering. The main command is FeatureLinesStyleExtra. The project also includes the command FL_DUMPLOG for printing the active session log to the AutoCAD command line. The plugin is intended for Civil 3D users who need faster feature line creation, easier feature line style searching, command logging, and a more controlled conversion workflow. Project Type • 🧩 C# .NET Plugin — this is a compiled Civil 3D plugin project that builds a CivilFeatureLines.dll file. • 🪟 WPF User Interface — the project uses CreateFeatureLinesDialog.xaml and CreateFeatureLinesDialog.cs to display a custom settings window. • 📘 Documentation Included — the project includes README.md with build notes, commands, log format, and suggested improvements. • 🔴 Not A Standalone LISP — this uploaded project is not a single AutoLISP routine and does not include a LISP loader in the visible project files. Main Commands • 🚀 FeatureLinesStyleExtra — opens the feature line creation dialog and converts selected objects into Civil 3D feature lines. • 📋 FL_DUMPLOG — prints all in-memory session log entries to the AutoCAD command line. Loading Method • 🧰 Build DLL — open CivilFeatureLines.csproj in Visual Studio and build the project as x64. • 📦 Load Plugin — load the compiled CivilFeatureLines.dll in Civil 3D using NETLOAD. • 📌 Run Command — run FeatureLinesStyleExtra from the Civil 3D command line. • 📋 Review Log — run FL_DUMPLOG to print the current command session log. User Workflow • 🚀 Start Command — the user runs FeatureLinesStyleExtra in Civil 3D. • 📌 Select Objects — the command prompts the user to select objects that should be converted to feature lines. • 🧩 Collect Sites — the plugin reads available Civil 3D sites from the active drawing. • 🎨 Collect Feature Line Styles — the plugin reads feature line style names from the active Civil 3D document. • 🪟 Open WPF Dialog — the plugin opens the Create Feature Lines dialog. • 🌐 Choose Site — the user can select None for siteless feature lines or select an available Civil 3D site. • 🏷️ Set Name Template — the user can define the feature line name template used during creation. • 🎨 Assign Style — the user can enable style assignment and select a feature line style from the filtered list. • 🔍 Filter Styles — the user can search feature line styles with wildcard patterns such as * and ?. • 🧱 Choose Layer Mode — the user can choose a custom layer, the current layer, or the selected entity layer option. • 🧹 Choose Erase Option — the user can erase original source entities after feature line creation. • 📐 Assign Elevations — the user can request elevation assignment from a surface. • 🧹 Weed Points — the user can request the Civil 3D weed feature lines command after feature lines are created. • ✅ Confirm — the user clicks OK to create the feature lines. • 🔴 Cancel — the user clicks Cancel to close the dialog without creating feature lines. Functionalities • 🚀 Feature Line Creation — the plugin converts selected objects into Civil 3D feature lines using FeatureLine.Create. • 🌐 Site Selection — the dialog lets the user create siteless feature lines or assign new feature lines to an existing Civil 3D site. • 🔒 Correct Site Overload Handling — the code uses the two-argument FeatureLine.Create overload when the site is None, avoiding the Civil 3D error caused by passing ObjectId.Null as a site ID. • 🎨 Feature Line Style Assignment — when enabled, the plugin assigns the selected Civil 3D feature line style by setting StyleId on the created feature line. • 🔍 Wildcard Style Search — the style list supports * for any characters and ? for a single character. • 🏷️ Feature Line Naming — the plugin uses a name template and replaces the next-counter token with a four-digit sequence number. • 🧱 Custom Layer Creation — when custom layer mode is selected, the plugin checks whether the layer exists and creates it if needed. • 🧱 Layer Assignment — when a layer name is resolved, the created feature line layer is set through the feature line Layer property. • 📐 Elevation Assignment — when enabled, the plugin calls AssignElevationsFromSurface using ObjectId.Null to use the first available surface. • 🧹 Source Entity Erase — when enabled, the original selected source entity is erased after the feature line is created. • 🧹 Weed Points Workflow — when enabled, the plugin queues _AeccWeedFeaturelines after creation and asks the user to select the newly created feature lines when Civil 3D prompts. • 🔒 Document Locking — the command uses DocumentLock before Civil 3D database writes to reduce write failures. • 🧩 Transaction Handling — feature line creation, style assignment, layer assignment, elevation assignment, and source erasing are wrapped inside an AutoCAD transaction. • 📋 Command Logging — the plugin logs command progress, warnings, failures, selected options, and conversion results. • 💾 Daily Log Files — logs are saved under %APPDATA%\CivilFeatureLines\Logs with daily file names. • 📘 Version Banner — when the DLL loads, the plugin prints a version banner using the assembly version and DLL creation timestamp. • 🪟 Help Button — the WPF dialog includes a Help button explaining wildcard style filter examples. Important Helper Logic • 🚀 Plugin Entry Point — App.Initialize starts file logging, prints the version banner, and reports available commands when the DLL is loaded. • 📋 Logger Singleton — CommandLogger.Instance provides shared command-line and file logging for the whole plugin. • 💾 File Logging — EnableFileLogging creates the log folder and writes daily log files named like FeatureLines_yyyy-MM-dd.log. • 📋 Session Log Dump — DumpSessionLog prints the in-memory session log to the AutoCAD command line. • 📘 Version Builder — BuildVersionString reads the executing assembly version and DLL last-write time to build the load banner. • 🧩 Site Collector — GetSiteNames reads Civil 3D site names from CivilDocument.GetSiteIds. • 🎨 Style Collector — GetFeatureLineStyleNames reads available styles from cdb.Styles.FeatureLineStyles. • 🌐 Site Resolver — ResolveSiteId finds the selected Civil 3D site object ID by name. • 🎨 Style Resolver — ResolveFeatureLineStyleId finds the selected feature line style object ID by name. • 🧱 Layer Resolver — ResolveTargetLayer decides whether the command should use custom, current, or selected-entity layer behavior. • 🧱 Layer Creator — EnsureLayerExists creates the custom target layer when it does not exist. • 🔍 Wildcard Converter — WildcardToRegex converts wildcard style filters into anchored regular expressions. • 🔍 Filter Logic — ApplyFilter updates the visible feature line style list based on the wildcard filter text. • ✅ Dialog Result Builder — BtnOK_Click validates style selection and builds the CreateFeatureLinesOptions result object. Important Code Notes • 📌 Command Name — the main command name is FeatureLinesStyleExtra. • 🔴 Platform Requirement — this project requires Autodesk Civil 3D because it uses Civil 3D APIs such as FeatureLine, Site, CivilDocument, and FeatureLineStyle. • 🔴 Build Requirement — the project targets .NET Framework 4.8, uses WPF, targets x64, and requires AutoCAD and Civil 3D managed references. • 🔴 Props File Requirement — the project imports a machine-specific ObjectARX and Civil 3D reference props file from a OneDrive path. If that file is missing, the project may not build until the import path is corrected. • 🔴 Output Path Note — the project redirects bin and obj output to LocalAppData to avoid OneDrive sync locks and long path problems. • 🔴 Assign Name Limitation — the dialog includes an AssignName option, but the visible command code always builds the feature line name from the template and does not branch on AssignName. • 🔴 Selected Entity Layer Limitation — the dialog includes a Use selected entity layer option, but the visible layer resolver returns null for that mode and does not explicitly set each new feature line to the source entity layer. • 🔴 Elevation Surface Limitation — AssignElevationsFromSurface is called with ObjectId.Null, meaning the code relies on Civil 3D behavior for the first available surface and does not provide a surface picker. • 🔴 Weed Points Limitation — the managed API does not weed points directly here. The plugin queues the native _AeccWeedFeaturelines command and the user must follow the Civil 3D prompt. • 🔴 Undo Limitation — the README notes undo grouping as a suggested improvement, so the visible code does not implement a named one-step undo group for the whole batch. • 🔴 No AutoLISP Loader Note — the visible zip contents do not include an AutoLISP loader file. The plugin is loaded with NETLOAD after building the DLL. Final Result The final result is a Civil 3D feature line creation workflow with a custom searchable WPF dialog. The user selects source objects, chooses a site, optional style, layer behavior, erase option, elevation assignment, and weed-point option, then creates Civil 3D feature lines with detailed command logging. This improves productivity, speeds up style selection, reduces repetitive Civil 3D dialog work, helps with QA tracking through logs, and gives Civil 3D users a more controlled workflow for creating feature lines from objects.