SOLVED

Sharepoint 2019- develop Visual webpart with SQL database

%3CLINGO-SUB%20id%3D%22lingo-sub-1326977%22%20slang%3D%22en-US%22%3ESharepoint%202019-%20develop%20Visual%20webpart%20with%20SQL%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1326977%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20planning%20to%20implement%20SharePoint%202019%20on-prem%20to%20replace%20the%20existing%20SP%202010%20intranet.%20we%20have%20a%20few%20SP%20visual%20webparts%20with%20SQL%20data%20sources%20that%20were%20build%20using%20VB.net%20.%20we%20like%20to%20know%20if%20it%20is%20possible%20to%20migrate%20SP2010%20.wsp%20solution%20to%20SP2019%20(webpart%20-server-side%20%2FClient%20side)%20or%20any%20clear%20guidelines%2Finstructions%20on%20how%20to%20develop%20visual%20webpart%20solutions%20(with%20SQL%20database)%20for%20SP%202019%20on-premise.%3C%2FP%3E%3CP%3EI%20do%20apologize%20for%20my%20lack%20of%20understanding%20of%20all%20this%20different%20framework.%20Thanks%20in%20advance%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1329680%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202019-%20develop%20Visual%20webpart%20with%20SQL%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1329680%22%20slang%3D%22en-US%22%3EYou%20won't%20be%20able%20to%20fully%20migrate%3CBR%20%2F%3EThe%20best%20solution%20would%20be%20to%20create%20a%20REST%20API%20to%20expose%20the%20data%20from%20the%20SQL%20database%20and%20then%20create%20a%20SharePoint%20framework%20solution%20to%20consume%20that%20data%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1330476%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202019-%20develop%20Visual%20webpart%20with%20SQL%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1330476%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9907%22%20target%3D%22_blank%22%3E%40Joel%20Rodrigues%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20valuable%20reply.%20looks%20like%20it%20is%20over%20complicated%20what%20SP2010%20used%20to%20do.%20simply%20develop%20and%20hosting%20solutions%20for%20business%20with%20any%20databases.%3C%2FP%3E%3CP%3Eit's%20really%20frustrating%20Microsoft%20overkill%20product%20without%20any%20road%20map.%20I%E2%80%99m%20not%20sure%20what%20is%20going%20be%20the%20reaction%20from%20millions%20of%20businesses%20and%20developers%26nbsp%3Bspend%20time%20and%20money%20into%20Microsoft%20now%20they%20can%E2%80%99t%20do%20very%20simple%20basic%20solutions%20without%20over%20complicating.%26nbsp%3B%3C%2FP%3E%3CP%3Ealso%2C%20I%20can%E2%80%99t%20find%20any%20MS%20guideline%20(look%20like%20no%20one%20knows%20in%20MS)or%20step%20by%20step%20documentation%20for%20how%20to%20develop%20SP%202019%20Hosted%20APP%20that%E2%80%99s%20work%20with%20external%20API%26nbsp%3B%20without%20using%20beloved%20azure.%3C%2FP%3E%3CP%3EAppreciate%20if%20you%20can%20provide%20any%20documentation.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%20for%20your%20reply%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1330627%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202019-%20develop%20Visual%20webpart%20with%20SQL%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1330627%22%20slang%3D%22en-US%22%3EThis%20actually%20may%20sound%20more%20complex%20in%20the%20beginning%2C%20but%20it's%20a%20lot%20easier%20in%20practice%20as%20Microsoft%20does%20a%20lot%20of%20the%20work%20behind%20the%20scenes.%3CBR%20%2F%3EPrevious%20development%20models%20(like%20we%20had%20in%20SharePoint%202010)%20were%20simply%20not%20feasible%20and%20reliable%20for%20scaling%20to%20the%20cloud%20level.%3CBR%20%2F%3E%3CBR%20%2F%3ECheck%20out%20this%20video%20as%20an%20example%20for%20your%20scenario%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fyoutu.be%2FSDjKRfHA1nw%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fyoutu.be%2FSDjKRfHA1nw%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20summary%2C%20if%20your%20secure%20your%20API%20with%20Azure%20AD%2C%20which%20you%20can%20easily%20do%2C%20you%20can%20then%20consume%20the%20API%20from%20a%20SharePoint%20framework%20solution%20without%20having%20to%20fully%20handle%20the%20authentication.%20It's%20done%20behind%20the%20scenes.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20another%20option%20could%20be%20to%20use%20PowerApps%20and%20connect%20directly%20to%20the%20SQL%20database%2C%20but%20I%20haven't%20done%20that%20yet%20so%20perhaps%20someone%20else%20could%20comment%20on%20that.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1330704%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202019-%20develop%20Visual%20webpart%20with%20SQL%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1330704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9907%22%20target%3D%22_blank%22%3E%40Joel%20Rodrigues%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20your%20reply%20and%20the%20link.%20looks%20like%20lost%20of%20issues%20getting%20user%20authenticated%20to%20start%20with.%20it's%20using%26nbsp%3Bstage%20hammer%20to%20crack%20an%20egg.%3C%2FP%3E%3CP%3EI'm%20only%20looking%20at%20Sp2019%20On-premise%20server%20farm%20not%26nbsp%3B%20SP%20online%20(%3CSPAN%3Ecloud%26nbsp%3B%3C%2FSPAN%3E)%20!%3C%2FP%3E%3CP%3Ewe%20don't%20see%20any%20use%20case%20going%20with%20cloud%20for%20webpart%20we%20have%20with%20all%20the%20limitations%20red%20tag%20with%20SPOnline%20.that's%20why%20most%20of%20the%20businesses%20like%20us%20stay%20away%20from%20SP%20online.%3C%2FP%3E%3CP%3Ewith%20new%20SP2019%20On-premise%20we%20though%20we%20have%20a%20hope%20to%20migrate%20aging%20Intranet%20but%20it%20seems%20that%20it%20just%20falls%20hope%20and%20not%20worth%20investing%20time%20and%20money%20on%20MS%20making%20over%20complex%20and%20hard%20manage%20solutions%20for%20an%20organization%20like%20us.%3C%2FP%3E%3CP%3Eanyway%2C%20thanks%20for%20your%20valuable%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We are planning to implement SharePoint 2019 on-prem to replace the existing SP 2010 intranet. we have a few SP visual webparts with SQL data sources that were build using VB.net . we like to know if it is possible to migrate SP2010 .wsp solution to SP2019 (webpart -server-side /Client side) or any clear guidelines/instructions on how to develop visual webpart solutions (with SQL database) for SP 2019 on-premise.

I do apologize for my lack of understanding of all this different framework. Thanks in advance

4 Replies
Highlighted
Best Response confirmed by Beau Cameron (MVP)
Solution
You won't be able to fully migrate
The best solution would be to create a REST API to expose the data from the SQL database and then create a SharePoint framework solution to consume that data
Highlighted

@Joel Rodrigues 

Thanks for your valuable reply. looks like it is over complicated what SP2010 used to do. simply develop and hosting solutions for business with any databases.

it's really frustrating Microsoft overkill product without any road map. I’m not sure what is going be the reaction from millions of businesses and developers spend time and money into Microsoft now they can’t do very simple basic solutions without over complicating. 

also, I can’t find any MS guideline (look like no one knows in MS)or step by step documentation for how to develop SP 2019 Hosted APP that’s work with external API  without using beloved azure.

Appreciate if you can provide any documentation.  

Thanks again for your reply

Highlighted
This actually may sound more complex in the beginning, but it's a lot easier in practice as Microsoft does a lot of the work behind the scenes.
Previous development models (like we had in SharePoint 2010) were simply not feasible and reliable for scaling to the cloud level.

Check out this video as an example for your scenario
https://youtu.be/SDjKRfHA1nw

In summary, if your secure your API with Azure AD, which you can easily do, you can then consume the API from a SharePoint framework solution without having to fully handle the authentication. It's done behind the scenes.

I think another option could be to use PowerApps and connect directly to the SQL database, but I haven't done that yet so perhaps someone else could comment on that.
Highlighted

@Joel Rodrigues  Thanks for your reply and the link. looks like lost of issues getting user authenticated to start with. it's using stage hammer to crack an egg.

I'm only looking at Sp2019 On-premise server farm not  SP online (cloud ) !

we don't see any use case going with cloud for webpart we have with all the limitations red tag with SPOnline .that's why most of the businesses like us stay away from SP online.

with new SP2019 On-premise we though we have a hope to migrate aging Intranet but it seems that it just falls hope and not worth investing time and money on MS making over complex and hard manage solutions for an organization like us.

anyway, thanks for your valuable reply.