.sujenanth
09/09/2023, 11:24 AMAnders Bjerner
09/09/2023, 1:55 PMKevin Jump
09/09/2023, 1:58 PMwwwroot/App_Plugins
, this should be part of the published package when the site is built, there are more detailed and complex ways, essentially you should treat the custom code like a package. https://docs.umbraco.com/umbraco-cms/extending/packages/creating-a-package and then they will deploy more like code and can be moved between soloutions, but i think moving to wwwroot/App_Plugins
, is the quick and dirty way of you not having to seperatly clone them (umbraco merges /App_Plugins and wwwroot/App_Plugins
, so they look like one folder).
Also , and i can't remember this there is a setting you can add to the .csproj to make /App_Plugins be part of the published site, (then you wouldn't have to move themAnders Bjerner
09/09/2023, 2:05 PMwwwroot
folder, but there shouldn't be any problem in doing so.
To ensure that App_Plugins files are in fact copied to the output directory when doing a deploy, you can add something like this to your .csproj file:
xml
<ItemGroup>
<Content Include="App_Plugins\YourName\**\*">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
<Content Include="App_Plugins\YourName.Section1\**\*">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
<Content Include="App_Plugins\YourName.Section2\**\*">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
</ItemGroup>
or something like:
xml
<ItemGroup>
<Content Include="App_Plugins\**\*">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
</ItemGroup>
Kevin Jump
09/09/2023, 2:33 PMAnders Bjerner
09/09/2023, 2:58 PMAmbert
09/09/2023, 5:18 PMAmbert
09/09/2023, 5:18 PM.sujenanth
09/10/2023, 4:37 PMProBot β¨
09/10/2023, 4:37 PM.sujenanth
09/10/2023, 4:38 PMAnders Bjerner
09/10/2023, 6:51 PM.sujenanth
09/11/2023, 7:27 AM.sujenanth
09/11/2023, 7:27 AM.sujenanth
09/11/2023, 7:28 AMAnders Bjerner
09/11/2023, 7:30 AM.sujenanth
09/11/2023, 7:33 AM.sujenanth
09/11/2023, 7:33 AMAnders Bjerner
09/11/2023, 7:36 AMAnders Bjerner
09/11/2023, 7:39 AM.sujenanth
09/11/2023, 8:29 AMAnders Bjerner
09/11/2023, 8:31 AMAnders Bjerner
09/11/2023, 8:33 AM"bundleOptions": "None"
to your package.manifest
..sujenanth
09/11/2023, 8:53 AMAnders Bjerner
09/11/2023, 8:57 AMbundleOptions
in your manifest, all backoffice extensions get merged into one .js
file. That's the umbraco-backoffice-extensions-js.js
that you can see from your last screenshot.
By adding "bundleOptions": "None"
it should tell Umbraco to not bundle or minify your JS files, but serve them individually. There is also "bundleOptions": "Independent"
, which tells Umbraco to create a separate bundle for your files..sujenanth
09/11/2023, 9:00 AM