Forum Discussion
Ongoing support for .aspx pages launched from document libraries
Hi euank
The approach of storing the .aspx file directly in the library is not recommended by Microsoft. Using this approach will cause more security issues and whoever has permission can download or modify the file. The best practice is to use the SharePoint Framework(SPFx) development model which is more secure and you can implement a lot of features without any restrictions. You can get the full details on the link below.
Sudharsan K Thanks so much for taking the time to respond!
I appreciate your guidance: I'm definitely aware of the security considerations, and of SpFx, and indeed the context for my question is essentially, how long do we have to progressively migrate the current apps to SpFx (or other supported scenario) - e.g. is it possible to know when this 'feature'/capability will cease to work?
Do you have a reference for "The approach of storing the .aspx file directly in the library is not recommended by Microsoft."? Is there an explicit statement from MSFT somewhere about this?
- Would also appreciate some clarity on this!
I am also searching for a solution to this exact issue.
- I believe they put something out in the SharePoint alerts/0365 updates.
Not a big deal, frustrating in that it now takes more of a developer then it use to. There's not a lot of us dedicated to this.
Next we have the SPFX preview is down. You cannot interact with the build in the workbench. MS has had a ticket open with me for a month now and nothing is better.
While SPFX is the better path, you broke break the valuable workbench.aspx in the process. You'll be in a world of hurt for the future if you keep neutralizing valuable means without alternatives. This is still a CMS. Not everyone is built for DevOps.
