jesperhoy/VueJSWebForms

This system is a .NET library that integrates Vue.js with ASP.NET Web Forms, allowing developers to use single-file .vue components within traditional Web Forms pages. It provides server-side controls that compile and cache Vue templates, support external script references, and handle client-side postback events. The library manages the bridge between the server-side Web Forms lifecycle and client-side Vue rendering.

The library has been rebranded from 'Vue Light' to 'Vue.js ASP.NET Web Forms helpers', with all internal assembly titles, product names, and resource namespaces updated to reflect the new 'VueJSWebForms' identity. Additionally, the assembly version has been incremented to 3.3.0.0, and the copyright period has been extended to 2021.

src/My Project · high confidence

The sample web site has been updated to use the renamed VueJSWebForms library instead of the previous VueLightWebForms. This involves renaming the ScriptTemplate control to ServerTemplate, updating the assembly and namespace references in the ASPX pages, and adjusting the sample pages (sample-servertemplate.aspx, sample-vue-file.aspx, sample-vuejs.aspx) to use the new control prefixes and attributes. The index.html page has also been updated to reflect these changes in its navigation links and titles.

sample-web-site · high confidence

The library has been renamed from VueLightWebForms to VueJSWebForms. The new Component and App controls replace the previous Compile/RenderTemplate modes with a unified approach that supports .vue single-file components. A key behavioral change is the addition of server-side caching for .vue files (using the CacheDependency on file changes) and support for external JavaScript references via \<script src="..."\> tags within .vue files. The Component control now requires either a 'File' or 'Name' property and supports a 'SquashWS' option to control whitespace handling in templates. Additionally, both Component and App controls now implement IPostBackEventHandler, enabling client-side postback events to be raised to the server.

src · high confidence

The project has been renamed from VueLightWebForms to VueJSWebForms, updating the root namespace, assembly name, and documentation file references. Additionally, the codebase underwent structural cleanup: the System.Data reference was removed, and source files were renamed or replaced (modHelpers to Module1, ScriptTemplate to ServerTemplate, Compiler to VueApp, and VueRender removed), while new files VueApp and VueFilesToJS were added.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• First survey — no prior run to compare against. CAI 45.

• Code Health 97
• Architecture 69
• Maturity 46
• Readiness 23
• Security 100

• 27 commits — 25 feature/other, 2 fixes

• (root) — 20 commits
• sample-web-site/Bin — 4 commits
• src/My Project — 2 commits
• src/Compiler.vb — 1 commit

• fix: Fix template string escaping
• fix: Fixed: Compiler threw exception is root element contained v-if
• change: Added .vue file component, renamed project "VueLightWebForms -> VueJSWebForms", renamed control attribute "Compile" -> "VueLight"
• change: Added JSBuilder utility class
• change: Added NuGet info to readme
• change: Added support for external JavaScript file reference in .vue files (<script src="...">)
• change: First commit
• change: Update to v. 1.1.1
• change: Updated readme
• change: Updated readme
• change: When rendering Render/Component controls with compile=false / rendertemplate=false, remove whitespace and in-line template
• change: update version number and references
• change: updated readme
• change: updated readme
• change: updated readme
• change: updated readme
• change: updated readme
• change: updated readme
• change: updated readme
• change: updated readme again
• …and 7 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

jesperhoy/VueJSWebForms was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.