This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 9%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESB%3C/text%3E%3C/svg%3E)
In Visual Studio 2022, the new version .NET 9.0 project template ".NET MAUI Blazor Hybrid and Web App" will create the following projects in a new solution:
Where would you put the resources? Currently, I have them in ProjectName under the following path:
Resources/raw
This works well for Windows, Android, and iPhone. But how do I access these for web? I would prefer they exist in the same location. In my particular use case, these are the same files I use for all 4 platforms. Some of them are large language models and I would rather not keep duplicates around.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 6%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELL%3C/text%3E%3C/svg%3E)
Where would you put the resources?
Please share the type of resources that you want to put, such as Images or other texts?
If you want to put the large language models, save them to the ProjectName.Shared
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
you question is not clear. if you mean compiled resources, then share makes a good case. if you mean actual files, then they are copied to target folders at build time which will vary by project type. note: the project dll files (which are not small) get copied on build.