Forums Home / ComponentOne / ASP.NET Web Forms Edition
Posted by: enrique.pv-ext on 30 July 2026, 10:41 am EST
enrique.pv-ext
Posted 30 July 2026, 10:41 am EST - Updated 30 July 2026, 11:01 am EST
Hi,
Migrate from 2010v1 to 2025v2 399 in ASP.NET WebForms NET Framework 4.8.1.
Using Controls from C1.Web.Wijmo.Controls.48.dll
LEGACY
new Wijmo
any suggestions or approach to use LEGACY css / styles to apply new controls ??
classes changed…
uttkarsh.matiyal
Posted 31 July 2026, 3:03 am EST
Hello Enrique,
Apologies for the inconvenience. Unfortunately, the legacy Themes/CSS cannot be used with the latest version because the client-side HTML structure, CSS class names, and overall architecture have changed significantly between the versions.
The recommended approach is to use the themes and styling provided with the latest version, as they are designed to work with the updated HTML and CSS structure.
see: Theming | Getting Started with ASP.NET Web Forms
Regards,
Uttkarsh.
enrique.pv-ext
Posted 3 August 2026, 10:39 am EST
give me more ideas or samples about it ?
change CSS for legacy to new ?
Control 2010 to Control 2025
CSS legacy → CSS new
Matrix mapping legacy vs new CSS, maybe get html + css render in old pages (Playwright, Selenium,
Screenshot automation…)
Create legacy-look.css ??
uttkarsh.matiyal
Posted 3 August 2026, 11:31 pm EST
Hello Enrique,
I understand the migration effort involved, and I wish I had a simpler answer. However, we’re not able to provide a complete legacy-to-new CSS/class mapping or a ready-made ‘legacy-look.css’ for a few reasons:
Instead, I’d recommend using the built-in themes in the current version as the baseline (as shared in my earlier reply).
If there are specific visual differences that affect usability or functionality, please share the control and some screenshots. We can then help identify the closest CSS classes/variables available in the new version.
I understand this may not be the complete solution you were hoping for, but we’re happy to help with specific control-by-control questions during the migration.
Regards,
Uttkarsh.
enrique.pv-ext
Posted 7 August 2026, 7:55 am EST
thanks for all explains.
I have now (legacy)…
StylesheetTheme=“Sep” Theme=“Sep”
<%@ Page Language="C#" AutoEventWireup="True" CodeBehind="Default.aspx.cs" Inherits="WebApp.Login.Default"
StylesheetTheme="Sep" Theme="Sep"
MasterPageFile="~/MasterPage.master" EnableEventValidation="true" %>
<asp:Content ID="Content3" runat="server" ContentPlaceHolderID="ContentHead">
<link href="~/VisualStyles/CustomVisualStyle2/C1Window/styles.css" type="text/css" />
</asp:Content>StylesheetTheme=“Content” Theme=“Content”
<%@ Page Language="C#" AutoEventWireup="True" CodeBehind="Default.aspx.cs" Inherits="WebApp.Default"
StylesheetTheme="Content" Theme="Content" MasterPageFile="~/ContentMasterPage.master" %>
Resumen EjecutivoEl proyecto utiliza un sistema de estilos multi-capa basado en dos arquitecturas diferentes:
Estructura de CarpetasPROJECT/
├── App_Themes/ [11 archivos CSS]
│ ├── Content/
│ │ ├── ContentStyle.css ⭐ PRINCIPAL (130 KB)
│ │ └── Imagenes/ (recursos)
│ ├── Sep/
│ │ ├── estiloSEP.css ⭐ ESTILO LOGIN/BASE (25 KB)
│ │ ├── estiloSEP.TransitsReports.css
│ │ └── Imagenes/
│ ├── Menu/
│ │ ├── Vista/C1Menu/styles.css
│ │ ├── Office2007Blue/C1Menu/styles.css
│ │ ├── Office2007Silver/C1Menu/styles.css
│ │ ├── Office2007Black/C1Menu/styles.css
│ │ ├── ArticFox/C1Menu/styles.css
│ │ └── VistaBlack/C1Menu/styles.css
│ └── SepExtNet.css ⭐ ESTILOS EXT.NET (principal)
│
├── VisualStyles/ [28 archivos CSS]
│ ├── CustomVisualStyle/ (estilo corporativo SEP)
│ │ ├── C1Window/styles.css
│ │ ├── C1Menu/styles.css
│ │ ├── C1ComboBox/styles.css
│ │ └── C1Input/styles.css
│ ├── CustomVisualStyle2/ ⭐ (variante corporativa)
│ │ └── C1Window/styles.css (21 KB)
│ └── Vista/ (estilo por defecto C1)
│ ├── C1Window/styles.css
│ ├── C1Menu/styles.css
│ ├── C1GridView/styles.css
│ ├── C1Input/styles.css
│ ├── C1ComboBox/styles.css
│ ├── C1TabControl/styles.css
│ ├── C1Calendar/styles.css
│ ├── C1TreeView/styles.css
│ ├── C1ToolBar/styles.css
│ ├── C1Upload/styles.css
│ ├── C1Splitter/styles.css
│ ├── C1ProgressBar/styles.css
│ ├── C1NavPanel/styles.css
│ ├── C1Schedule/styles.css
│ ├── C1HeaderContentControl/styles.css
│ ├── C1MultiPage/styles.css
│ ├── C1TabStrip/styles.css
│ ├── C1ToolTip/styles.css
│ ├── C1Slider/styles.css
│ ├── C1Accordion/styles.css
│ ├── C1FormDecorator/styles.css
│ ├── C1Editor/styles.css
│ └── C1Expander/styles.css
│
└── js/jquery/skins/ [2 archivos CSS]
├── tango/skin.css
└── amg/skin.css
Sistema de Temas (Themes)A nivel de Página (.aspx):
<%@ Page ... StylesheetTheme="Content" Theme="Content" %>
Diferencia entre StylesheetTheme y Theme:
StylesheetTheme="Content"Theme="Content"Uso en el proyecto:
StylesheetTheme="Content"StylesheetTheme="Sep"Archivo:
App_Themes/Content/ContentStyle.cssCaracterísticas:
#e6e6e6fondo_contenido_up.pngTahoma, Geneva, sans-serif; 11px#006enrique.pv-ext
Posted 7 August 2026, 8:08 am EST
Web.config - Configuración relevante para CSS
• Línea 75: ChartImageHandler apunta a App_Themes/Content/Imagenes/
• Líneas 102-110: con acceso anónimo 
Crítico
• Línea 277: viewStateEncryptionMode=“Always” (puede impactar rendimiento)
• Línea 642: Ext.NET theme=“Triton”
• Handlers para recursos .axd (ScriptResource, WijmoControlsResource)
Hallazgos clave para migración:
• Los temas se aplican mediante StylesheetTheme=“Content” en directivas @Page
• Requiere acceso anónimo a App_Themes o los estilos no cargan antes del login
• Paleta corporativa definida (#006, #e6e6e6 , #ffd82f , #0BB5FF )
• 3 sistemas de estilos coexistiendo (WebForms native, ComponentOne, Ext.NET)
uttkarsh.matiyal
Posted 10 August 2026, 1:50 am EST
Hello Enrique,
Thank you for sharing the detailed breakdown of your theming structure. That provides helpful context.
Since the new Wijmo-based controls use a different styling approach, there is no direct one-to-one alternative to the existing combination of App_Themes, C1 VisualStyles, and Ext.NET. Instead, the recommended approach would be to create a new styling theme for the Wijmo controls that aligns with your existing corporate look and feel.
One tool you can use to help create and customize this theme is jQuery ThemeRoller, which allows you to customize colors, fonts, and other visual properties:
https://help.grapecity.com/wijmo/3/webframe.html#ThemeRoller.html
This could help you achieve a closer match to your corporate color palette (‘#006’, ‘#e6e6e6’, ‘#ffd82f’, and ‘#0BB5FF’) when developing the new theme, rather than trying to maintain a separate CSS file that maps directly to the legacy styling.
If you can point us to 2–3 specific controls or screens where the visual differences are most critical, we can look into the control-specific CSS classes and determine how they can be customized to better match your existing styling.
Regards,
Uttkarsh
enrique.pv-ext
Posted 10 August 2026, 6:12 am EST
create a new styling theme for the Wijmo controls ??
PROYECTO/
├── App_Themes/
│ ├── Wijmo/
and DELETE legacy themes ??
Theme Menu/
App_Themes/Menu/ Vista/
App_Themes/Menu/ Office2007Blue/...
VisualStyles/CustomVisualStyle/
VisualStyles/ CustomVisualStyle2/
VisualStyles/Vista/
PROYECTO/
├── App_Themes/
│ ├── Menu/
│ │ ├── Vista/C1Menu/styles.css
│ │ ├── Office2007Blue/C1Menu/styles.css ...
│
├── VisualStyles/
│ ├── CustomVisualStyle/
│ │ ├── C1Window/styles.css
│ │ ├── C1Menu/styles.css ...
│ ├── CustomVisualStyle2/ ⭐ (variante corporativa)
│ │ └── C1Window/styles.css (21 KB)
│ └── Vista/
│ ├── C1Window/styles.css
│ ├── C1Menu/styles.css
│ ├── C1GridView/styles.css ...
│ └── C1Expander/styles.css
LEGACY C1 ASPX:
<cc1:C1GridView
runat="server"
VisualStylePath="~/VisualStyles"
UseEmbeddedVisualStyles="false"
VisualStyle="Vista"
...>
</cc1:C1GridView>
legacy properties:
VisualStylePathUseEmbeddedVisualStylesVisualStyleany suggestions?
kartik.dua
Posted 11 August 2026, 4:49 am EST
Hello Enrique,
Thanks for the detailed breakdown - this helps clarify the scope.
→ On removing the legacy theme folders:
Since the new Wijmo-based controls use a completely different CSS/DOM architecture, folders like App_Themes/Menu/Vista/, App_Themes/Menu/Office2007Blue/, VisualStyles/CustomVisualStyle/, VisualStyles/CustomVisualStyle2/, and VisualStyles/Vista/ will no longer be referenced once you’ve migrated the controls on a given page. That said, we’d recommend keeping them in source control (not deleting outright) until the migration is fully validated across all pages — some pages may still be on the legacy controls, and removing the folders early could break those.
→ On the legacy properties:
You’re right that VisualStylePath, UseEmbeddedVisualStyles, and VisualStyle are specific to the legacy C1 controls’ custom-visual-style mechanism and are no longer supported on the new Wijmo-based controls. Any markup using these properties will need to be removed when you swap in the new control — styling is now handled entirely via CSS.
→ On the Menu control specifically:
This has actually already been addressed in detail in your other thread here:
https://developer.mescius.com/forums/webforms-edition/styles-c1menu-from-2010v1-to-2025v2-399
To summarize the key points from that thread: the new C1Menu emits a minimal ul structure that’s transformed at runtime by the jQuery c1menu widget, so CSS must target the new elements (e.g., .wijmo-wijmenu-item, .wijmo-wijmenu-link) rather than the legacy ones. For the width/alignment issues you’re seeing, the recommended fixes are:
We have implemented a sample for your reference: Menu_Sample_Mod.zip
Please update the attached sample with your legacy implementation and share a screenshot showing the expected appearance. We’ll then try to reproduce the same visual behavior in the sample.
Regards,
Kartik
uttkarsh.matiyal
Posted 12 August 2026, 1:30 am EST
Hello Enrique,
Sure, please take your time updating the project.
Regarding the styling changes in C1GridView, please check the available Wijmo and jQuery UI themes and select the one that most closely matches your requirements. If the available themes do not meet your expectations, you can click “Create new theme…” in the designer to create a custom theme.
Please use Visual Studio 2019 to access the WebForms designer, as later versions of Visual Studio do not support the designer for these legacy controls.
See how to create a new custom theme: https://developer.mescius.com/componentone/docs/webforms/online-gettingstarted/rolling-a-theme.html
Regards,
Uttkarsh.
enrique.pv-ext
Posted 12 August 2026, 9:25 am EST
thanks!
I cannot install Visual Studio 2019 
can you attach any sample a custom theme , please mister ??
~/Content/themes/…
uttkarsh.matiyal
Posted 13 August 2026, 1:54 am EST
Hrllo Enrique,
Sure, please refer to the attached sample: GridView_CustomTheme.zip
Please let us know if you have any further queries or issues.
Regards,
Uttkarsh.
enrique.pv-ext
Posted 14 August 2026, 7:12 am EST - Updated 14 August 2026, 7:18 am EST
applies to c1menu too?
~/Content/themes/… overrides default WebResources.axd ? Handlers para recursos .axd (ScriptResource, WijmoControlsResource)
Using Theme asp.net or link CSS ?
https://help.grapecity.com/wijmo/3/webframe.html#IncludedThemes.html
<link href="http://cdn.wijmo.com/themes/stafford/jquery-wijmo.css" rel="stylesheet" type="text/css" />uttkarsh.matiyal
Posted 14 August 2026, 8:40 am EST
Hello Enrique,
Yes, these themes apply to all C1 WebForms controls. For more information, please refer to the following documentation:
Theming | Getting Started with ASP.NET Web Forms
In WebForms, you do not need to add CSS links manually. Only the following entry is required in the configuration file:
<appSettings>
<add key="WijmoTheme" value="~/Content/themes/sunny-custom/jquery-ui.css" />
</appSettings>
This entry is automatically added to the configuration file when a theme is applied through the designer.
Regards,
Uttkarsh
enrique.pv-ext
Posted 17 August 2026, 2:57 am EST
Thanks, WijmoTheme only required.
are there 8 Wijmo themes ?
I can download all themes here ?? https://help.grapecity.com/wijmo/3/webframe.html#IncludedThemes.html
Arctic
Aristo
Rocket
Midnight
Sterling
Cobalt
Lucid new!
Stafford new!
And JQuery UI Themes ??
uttkarsh.matiyal
Posted 17 August 2026, 9:06 am EST - Updated 17 August 2026, 9:11 am EST
Hello Enrique,
You can use Wijmo themes by adding a link to the desired theme in the ‘head’ section of your page, as shown below:
<head runat="server">
<title></title>
<link href="https://cdn.wijmo.com/themes/midnight/jquery-wijmo.css" rel="stylesheet" type="text/css" />
</head>
If you prefer to install the theme locally and use it in your project, you can open the CDN link for the desired theme, save its contents as a CSS file, and then reference that file in your project.
For jQuery UI themes, you can use the jQuery ThemeRoller. Navigate to Gallery, select a theme, customize it as needed, and then download it for use in your project.
Regards,
Uttkarsh.
enrique.pv-ext
Posted 18 August 2026, 2:12 am EST
I’m confusing.
Use 1:
<appSettings>
<add key="WijmoTheme" value="~/Content/themes/sunny-custom/jquery-ui.css" />
</appSettings>
or Use 2
<head runat="server">
<title></title>
<link href="https://cdn.wijmo.com/themes/midnight/jquery-wijmo.css" rel="stylesheet" type="text/css" />
</head>which is better option ? recommendations ? thx !!
uttkarsh.matiyal
Posted 18 August 2026, 3:02 am EST
Hello Enrique,
Since you cannot install VS2019 and therefore cannot use the theme editor to modify or preview themes, I would recommend using Option 2. You can directly obtain the theme and customize it according to your requirements using the online ThemeRoller, without any dependency on the Visual Studio theme editor.
However, if you do not need to modify the themes and intend to use them as-is, Option 1 would be the better approach. You can use the built-in themes directly, which also helps avoid unnecessary redundancy.
Regards,
Uttkarsh.
enrique.pv-ext
Posted 9 September 2026, 3:00 am EST
which difference Wijmo themes versus JQuery themes ?
enrique.pv-ext
Posted 9 September 2026, 4:44 am EST - Updated 9 September 2026, 7:08 am EST
Styles Legacy webapp
C1GridView using sytles.css from app_theme for C1GridView Vista
CSS + HTML custom for C1GridView legacy version
Theme default Wijmo (in WebResources.asxd)
CSS + HTML custom for C1GridView latest version
Apply midnight theme in my Master
<link href="https://cdn.wijmo.com/themes/midnight/jquery-wijmo.css" rel="stylesheet" type="text/css" />apply sterling theme in the Master page.
Head has several links:
link a /app_themes/content/ContentSytle
link a varios WebResource.asxd
link to https://cdn.wijmo.com/themes/sterling/jquery-wijmo.css
Using devTools , applies jquery-wijmo.css and WebResource styles:
in jquery-wijmo.css:
.ui-state-default a, .ui-state-default a:link, .ui-state-default a:visited {
color: #4c535c;
text-decoration: none;
}[/code]
color and text-decoration are strikethrough
in https://localhost:44341/WebResource.axd?d=9CF7...
[code].ui-state-default a, .ui-state-default a:link, .ui-state-default a:visited {
text-shadow: 0 1px 0 rgba(255, 255, 255, 0.8);
}apply similar styles (legacy) to C1Menu styles, C1GridView… in new version …
please, any help ?
$dll = "C:\GIT\repos\PROJECT\libs\ComponentOne\2025v2.399\bin\v4.8\C1.Web.Wijmo.Controls.48.dll"
$asm = [System.Reflection.Assembly]::LoadFrom($dll)
try {
$types = $asm.GetTypes()
} catch [System.Reflection.ReflectionTypeLoadException] {
$types = $_.Exception.Types | Where-Object { $_ -ne $null }
}
$type = $types | Where-Object { $_.Name -eq 'C1GridView' }
$type.FullName
$type.BaseType.FullName
$type.GetProperties() | Where-Object { $_.Name -match 'Theme|Style|Css|Skin|Visual|Resource|Class' } | Select-Object
Name, PropertyType | Format-Table -AutoSizeenrique.pv-ext
Posted 9 September 2026, 7:35 am EST - Updated 9 September 2026, 7:38 am EST
Copilot CLI for discover styles in dll:
adding markdown files
C:\GIT\repos\xxxxxx\libs\ComponentOne\2025v2.399\bin\v4.8\C1.Web.Wijmo.Controls.48.dll
[WebResource]El ensamblado embebe 64 ficheros
. Los relevantes para theming general y para .css
C1GridViewjquery-wijmo.cssCada uno de estos es equivalente al fichero que sirve
https://cdn.wijmo.com/themes/<tema>/jquery-wijmo.css| Recurso embebido | Nombre de tema |
|---|---|
|
arctic |
|
aristo |
|
aristo_mobile |
|
cobalt |
|
lucid |
|
metro |
|
metro_dark |
|
metro_mobile |
|
midnight |
|
moonlight_mobile |
|
ocean_mobile |
|
rocket |
|
rocket_mobile |
|
stafford |
|
sterling (usado actualmente vía CDN en el master) |
|
bootstrap |
|
jQuery Mobile (bundle base) |
WebResource.axdclass="wijmo-stylesheet-wijmo_theme"<head>| Recurso embebido |
|---|
|
|
|
|
|
Comentario embebido encontrado en el propio CSS (bundle de estructura, análogo a
jquery-ui.structure.cssIncludes: jquery.ui.core.css, jquery.ui.resizable.css, jquery.ui.selectable.css,
jquery.ui.accordion.css, jquery.ui.autocomplete.css, jquery.ui.button.css,
jquery.ui.datepicker.css, jquery.ui.dialog.css, jquery.ui.menu.css,
jquery.ui.progressbar.css, jquery.ui.slider.css, jquery.ui.spinner.css,
jquery.ui.tabs.css, jquery.ui.tooltip.css, jquery.ui.theme.css
uttkarsh.matiyal
Posted 10 September 2026, 9:01 am EST
Hello Enrique,
→ Wijmo themes vs. jQuery UI themes:
These are two separate systems that happen to coexist in C1 WebForms:
In practice, a Wijmo theme is really a themed jQuery UI skin with some extra Wijmo-specific styling layered on. You generally only need one or the other, not both, unless you’re intentionally overriding specific pieces.
→ On the conflicting-looking rules you found in DevTools:
The ‘.ui-state-default’ rules from ‘jquery-wijmo.css’ and from ‘WebResource.axd’ aren’t actually conflicting — they’re setting different properties (‘text-decoration’ vs ‘text-shadow’), so both apply. If you want to override either, target that specific selector in a stylesheet loaded after the theme CSS (higher in cascade order).
→ On matching your corporate colors for GridView/Menu:
Since you can’t use the VS2019 designer, your best path is:
I’ve had a look at the DLL resource dump you shared — that’s a solid reference for finding which embedded theme name maps to which resource path if you want to inspect one locally instead of pulling from CDN.
If there are still specific visual gaps (e.g., in GridView row/header styling) once you’ve applied a base theme, share screenshots of the specific mismatch and we can pinpoint the exact classes to override.
Regards,
Uttkarsh
enrique.pv-ext
Posted 11 September 2026, 8:14 am EST
match #006, #e6e6e6, #ffd82f, #0BB5FF ??
I’ll try Wijmo theme as a base, customize using jQuery ThemeRolle, (option 2), and override css maybe.
Then, latest, review C1 Controls, one to one…
thanks a lot
enrique.pv-ext
Posted 14 September 2026, 10:42 am EST
I try compare C1Menu in webapp legacy and now:
Comparación directa del HTML realmente renderizado por ambas apps sobre el mismo árbol de menú de producción (mismos textos/ítems: “Menú” → “Supervisión” → “Supervisión de centro”, etc.):
Legacy ( |
Actual ( |
|
|---|---|---|
| Motor de render | HTML propio del control ComponentOne Classic ( |
Widget |
| Clase raíz | |
|
| Ítem de menú | |
|
| Enlace clicable | |
|
| Texto | |
|
| Submenú desplegado | |
|
| Icono de módulo | |
|
| Separador | |
|
| Estados de interacción | |
|
| Profundidad de anidamiento | Explícita en el nombre de clase ( |
Implícita, solo por anidamiento real del DOM ( |
| Mecanismo de skin | Carpeta física de CSS ( |
CSS embebido como recurso del ensamblado (sin CSS de extensión propio, a diferencia de |
| Iconografía por módulo | 8 sprites |
Mismo icono genérico ( |
Ninguna clase del legacy (
, C1TextNode
, C1Link
, C1SubMenu-C1Vertical
, etc.) existe en el HTML Wijmo, y viceversa — exactamente el mismo tipo de incompatibilidad estructural ya diagnosticada para c1-h-flow
C1GridViewAnalisis-Migracion-Estilos-C1GridView.mdListado-Clases-CSS-C1Menu-Legacy.md-Wijmo48.mdHallazgo adicional — clases legacy puramente estructurales, sin ninguna regla CSS propia: el HTML legacy usa además
C1MenuC1Level0-3C1MenuItemC1FirstItemC1LastItemc1-h-childc1-v-childC1SubMenuContainerstyles.cssComparación línea a línea del HTML efectivamente devuelto por ambas apps para el mismo menú en tiempo de ejecución (mismo usuario, mismos ítems: “Menú” → “Supervisión” → “Supervisión de centro”, “Consolidación y contrastación”, etc.), no solo inferido de
styles.cssa) Contenedor raíz
| Legacy | Actual | |
|---|---|---|
| HTML | |
|
| Comentario de versión | |
Ninguno |
| Scroll (por nivel) | |
|
| Lista raíz | |
|
| Semántica ARIA | Ninguna | |
| Estado servidor (hidden input) | |
|
b) Ítem de menú con submenú (nodo
— ejemplo “Supervisión”)<li>
| Legacy | Actual | |
|---|---|---|
|
|
|
| Marcado de posición | |
Sin equivalente — no hay marcado de “primero/último” |
| Enlace | |
|
| Icono de módulo | |
|
| Texto | |
|
| Flecha de submenú | Ninguna marca explícita en el HTML (el despliegue lo gestiona JS vía |
|
| Submenú hijo (wrappers) | |
|
| Ítem hoja (sin hijos) | |
|
div.SubMenu > div.SubMenuContainer > div.ScrollContainer > ul<ul><a>C1Level0C1Level1C1Level2C1Level3ul ul ul li.wijmo-wijmenu-child .wijmo-wijmenu-childC1FirstItemC1LastItem<li>:first-child:last-child.gifico_supervision_off.gifico_fondoplaza_off.gifico_control_off.gifico_configuracion_off.gifico_informes_off.gifico_interfaces_off.gifico_mantenimiento_off.gifico_contrastacion_off.gifui-icon-arrowrefresh-1-s<span class="wijmo-wijmenu-text"><span class="wijmo-wijmenu-text"><img>.C1TextNode.wijmo-wijmenu-text > .wijmo-wijmenu-textC1*c1-h-flowc1-v-flowwijmo-wijmenu-*ui-*role="menu"role="menuitem"aria-haspopup="true"uttkarsh.matiyal
Posted 15 September 2026, 12:14 am EST
Hello Enrique,
We’re sorry, but it looks like your query got cut off midway and isn’t complete on our end. Could you please resend the rest, or let us know the exact questions you have?
From what we can see, you’ve shared a very detailed comparison and analysis of the legacy vs. new C1Menu HTML/DOM structure, along with your own suggestions for handling the migration (using descendant selectors for nesting depth, ‘:first-child’/‘:last-child’ for position, etc.) — and these are correct.
Please let us know what specific help you’re looking for so we can assist further.
Regards,
Uttkarsh
enrique.pv-ext
Posted 15 September 2026, 4:06 am EST
I have added a zip with:
C1MENU_HTML_Class_migrated_vs_legacy
3 markdowns:
Analysis about C1Menu styles legacy and migrated
CSS C1Menu legacy
CSS C1Menu Wijmo48
Wijmo C1Menu:
<div id="barra_menu">
<div style="float: left; z-index: 800000">
<div class="ui-widget ui-widget-header wijmo-wijmenu ui-corner-all ui-helper-clearfix" role="menu" style="width: 295px; height: 23px;">
<div class="scrollcontainer checkablesupport"><ul class="wijmo-wijmenu-list ui-helper-reset" id="ctl00_C1Menu1" style="height: 23px; width: 295px; display: block;" tabindex="0">Legacy C1Menu:
<div id="barra_menu">
<div style="float: left; z-index: 800000">
<!-- C1.Web.UI.Controls.3, 3.5.20101.174 http://www.componentone.com/ -->
<div id="C1Menu1" class="C1Menu C1Level0 C1Menu_CustomVisualStyle C1Menu_CustomVisualStyle-C1Horizontal" style="height:23px;width:295px;">
<div class="C1ScrollContainer" id="C1Menu1_ctl124" style="height:23px;width:295px;overflow:hidden;">
HTML + CSS classes changes Legacy C1Menu from Wijmo C1Menu.
I’m very confusing…
I’m cannot understand YET, " descendant selectors for nesting depth, ‘:first-child’/‘:last-child’ for position…" , I’ll try studing more, using IA for explains…
any help to apply CSS Legacy C1Menu to Wijmo C1Menu. ?
any help for mapping styles CSS classes and how-to applis CSS to new HTML wijmo C1Menu ??
enrique.pv-ext
Posted 15 September 2026, 6:20 am EST
With theme from https://jqueryui.com/themeroller/ is similar to sterling theme ?
Lista completa de temas disponibles en la Gallery de jQuery UI ThemeRoller (verificada en
https://jqueryui.com/themeroller/| # | Tema |
|---|---|
| 1 | Base |
| 2 | UI lightness |
| 3 | UI darkness |
| 4 | Smoothness |
| 5 | Start |
| 6 | Redmond |
| 7 | Sunny |
| 8 | Overcast |
| 9 | Le Frog |
| 10 | Flick |
| 11 | Pepper Grinder |
| 12 | Eggplant |
| 13 | Dark Hive |
| 14 | Cupertino |
| 15 | South Street |
| 16 | Blitzer |
| 17 | Humanity |
| 18 | Hot Sneaks |
| 19 | Excite Bike |
| 20 | Vader |
| 21 | Dot Luv |
| 22 | Mint Choc |
| 23 | Black Tie |
| 24 | Trontastic |
| 25 | Swanky Purse |
Nota: esta es la galería propia de jQuery UI ThemeRoller (framework CSS genérico). No incluye los nombres
,sterling,cobalt,lucid, etc., que corresponden al catálogo específico de temas Wijmo alojado en el CDN de Mescius (midnight). Ambos catálogos comparten estructura de clases CSS, por lo que ThemeRoller puede usarse para generar una variante compatible con Wijmo, pero no son la misma lista de temas.https://cdn.wijmo.com/themes/<nombre>/jquery-wijmo.css
enrique.pv-ext
Posted 15 September 2026, 6:55 am EST
sections in ThemeRoller:
Font SettingsCorner RadiusHeader/ToolbarContentDefault StateHover StateActive StateHighlightErrorOverlayShadowMapeo de la paleta corporativa a cada sección:
| Sección de ThemeRoller | Color corporativo a aplicar |
|---|---|
| Header/Toolbar (background + texto) | |
| Content (background) | |
| Default State (botones/bordes en reposo) | fondo |
| Hover State | |
| Active State | |
| Highlight | |
| Error | mantener el rojo por defecto, salvo que el corporativo defina uno propio |
| Overlay / Shadow | sin cambios respecto a la base elegida, ajustar solo si el diseño corporativo lo requiere |
Ajustar también Font Settings (tipografía) y Corner Radius si el estándar corporativo lo define.
I dont know now about this:
Header/Toolbar border ??
Content border, text ??
Hover State border, text ?
Active State border, text ?
Highlight border, text ?
Highlight ?
Font Settings (tipografía) ?
enrique.pv-ext
Posted 15 September 2026, 7:20 am EST
Download Builder – Download Custom Theme
Botón Download Theme → genera un ZIP con jquery-ui.css (o jquery-wijmo.css renombrado) + carpeta images/ (sprites ui-bg_.png, ui-icons_.png). Es imprescindible copiar también las imágenes; sin ellas se rompen bordes/iconos.
do I need ONLY jquery-ui.css + images ?
enrique.pv-ext
Posted 15 September 2026, 8:11 am EST - Updated 15 September 2026, 8:15 am EST
Custom jquery-ui.css load first in head,
then /ContentStyle.css
and latest is a WebREsource.axd.
<link href="/App_Themes/Sep/wijmo-custom/jquery-ui.css" rel="stylesheet" type="text/css">
<link href="../App_Themes/Content/ContentStyle.css" type="text/css" rel="stylesheet">
<link href="/WebResource.axd?d=G7A680" type="text/css" rel="stylesheet">can be jquery-ui.css loaded the last ?? is right ? how-to do it ?
En ContentMasterPage.master.cs :
protected override void OnPreRenderComplete(EventArgs e)
{
base.OnPreRenderComplete(e);
var customTheme = new HtmlLink { Href = ResolveUrl("~/App_Themes/Sep/wijmo-custom/jquery-ui.css") };
customTheme.Attributes["rel"] = "stylesheet";
customTheme.Attributes["type"] = "text/css";
Page.Header.Controls.Add(customTheme);
}uttkarsh.matiyal
Posted 16 September 2026, 6:48 am EST - Updated 16 September 2026, 7:04 am EST
Hello Enrique,
Thanks for providing the details.
Let me address the two simpler points first:
For the remaining issues, such as the title bar color not being applied, the Cancelar/Aceptar buttons losing their background or border, the faint checkboxes, and potential load-order issues, we would largely be guessing based on the screenshots. That could lead to a lot of back-and-forth without necessarily getting us to a resolution.
Could you put together a small, stripped-down page that reproduces these issues? A Menu and a single Dialog should be sufficient. If possible, please also include a “current vs. expected” screenshot for each issue. This would allow us to identify the exact selector or required fix for each case much more quickly.
If putting together a stripped-down sample is not convenient, another option would be to open a ticket through our private support portal and share the full runnable project there. We can then download it and investigate the behavior properly on our end rather than trying to diagnose it from screenshots alone.
Regards,
Uttkarsh.
uttkarsh.matiyal
Posted 16 September 2026, 7:01 am EST
Hello Enrique,
I’d also like to request, if possible, that you respond in English. Since this is a detailed thread, translating each message back and forth may cause us to miss or misunderstand some points.
This will help us follow the discussion more accurately.
Regards,
Uttkarsh
uttkarsh.matiyal
Posted 16 September 2026, 7:07 am EST
Hello Enrique,
Could you please share the “c1menu_overrides.css” file, along with any other custom changes you have made, and the exact theme you are currently using? This will help us put together a sample and investigate the issue further.
Regards,
Uttkarsh
enrique.pv-ext
Posted 16 September 2026, 7:15 am EST
custom theme roller UI light, and c1menu overrides
enrique.pv-ext
Posted 16 September 2026, 10:53 am EST - Updated 16 September 2026, 10:58 am EST
I’trry it. Now, I test styles for gridview:
It’s appears in display the /VisualStyles/Vista/C1GridView/Images/grid-horizontal.png in the bottom, very little part, view attached img:
Using custom styles (overrides)
CustomStyles_GridView.zip
and the legacy image \VisualStyles\Vista\C1GridView\Images for Gridview:
please any help ?
useful if attached HTML generated and styles (Page HTML and SAve as) ? for legacy and actual page ?
kartik.dua
Posted 17 September 2026, 4:36 am EST
Hello Enrique,
Thank you for sharing the details.
→ I try adjust heigh menu control, to 15px, but image background has height: 23px
We did not find any style where you have set menu-item height. For our implementation, refer to style section in Default.aspx in the attached sample.
→ Menu Items not aligns good
We did not observe this issue in our sample; Modify the attached sample to reproduce the behavior and we’ll investigate it.
→ It’s appears in display the /VisualStyles/Vista/C1GridView/Images/grid-horizontal.png in the bottom, very little part, view attached img:
we do not have “grid-horizontal.png” that you have used in .wijmo-wijpager class in c1gridview-overrides.css
→ useful if attached HTML generated and styles (Page HTML and SAve as) ? for legacy and actual page ?
Please share the steps you have taken, the code you are using, along with any relevant static files and screenshots comparing the expected layout with the current layout. It would also be helpful to know exactly what you are trying to implement and what is not working as expected.
Sample: GridView_Menu_Sample.zip
Regards,
Kartik
uttkarsh.matiyal
Posted 18 September 2026, 5:37 am EST
Hello Enrique,
We’re sorry, but we could not find a direct way to display connecting lines in TreeView. We have escalated it to the development team for further insights. [Internal Tracking ID: C1WEB-30749]
We’ll update you once we have more information.
We’d request you to open new ticket for separate concerns to avoid any misunderstandings. Discussing multiple things in a single thread may make it difficult to track each issue properly.
Regards,
Uttkarsh.
