Overall, I would choose option #1 if you really had to keep the files themselves in tact, otherwise I would opt for option #3 and convert them to Sitefinity pages. Hope this helps.
In your case "root" is likely the "Default" folder. It should have the app_data, sitefinity, bin, lib, etc folders in them.
Thanks for your post. Could you help further by advising further regarding Option 1?
After copying HTML files into root folder, what URL should be used for public users to access those HTML files through the website?
I'm still experiencing this challenge and hope you or someone can help. It seems I'm not the only one experience this challenge.
I tested but it didn't work out. Got the following error:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Other than copying the HTML files into the folder created in the root folder, anything else should be done? Anything needs to be configured in IIS or Sitefinity for this?
I tested your scenario by adding custom html file inside a folder named “CustomPages” . This folder should be placed on the root level of your project – where is the web.config file. Then you can access it through the url similar to the following:
If this doesn’t work in your scenario please make sure that you don’t have any limitation of the allowed file extensions in your IIS. Please have in mind that we handle in a special way request coming from folders with a certain names (like “Sitefinity”, “Images”, etc) so this could restrict you for accessing your files.
I figured it out the reason that caused that error.
I was uploading the files at OS level instead of through Sitefinity. When I tried uploading files through Sitefinity, it worked well.
A little bit inconvenient with Sitefinity uploading because I had to select each file one by one. But it is okay as long as it works.
I am glad to hear that the problem is resolved.