Menu
I've been asked to create a website in SharePoint within the next couple of weeks or so and I'm entirely new to SharePoint.
Does anyone have any good examples/tutorials on how to do some basic operations such as creating custom forms, using basic CRUD operations, with a custom SQL Server database?
Also is there any way to code in ASP.NET (with code-behind pages), but use the SharePoint look and feel and authentication stuff?
576
Organizations use Microsoft SharePoint to create websites. You can use it as a secure place to store, organize, share, and access information from any device. All you need is a web browser, such as Microsoft Edge, Internet Explorer, Chrome, or Firefox.
SharePoint provides a rich collaboration environment where people inside and outside your organization can work together, coauthoring document. Microsoft 365 provides a variety of options to help you create a secure and productive file collaboration environment that meets the needs of your organization.
You can develop SharePoint projects by using either Visual Basic or Visual C#, and you can develop app for SharePoint projects by using JavaScript.
Therefore, we've made the difficult decision to discontinue the SharePoint Online Public Website feature so that we can focus our efforts and investments on delivering capabilities in Microsoft 365 that will bring more value to our customers.
SharePoint is not quite like what you're used to. My two main gripes are:
Deployment:
If your requirements are for a single production site (no staging/test/development sites) your best bet is probably to go with the SharePoint Designer and hack stuff together directly on the production site (yes I know it's dirty).
If you need those other environments you should produce deployment packages for everything (no xcopy deployment). Deployment packages are a PITA IMHO and are very easy to get wrong.
IIS
SharePoint basically takes over your IIS installation and introduces a new set of rules for where things are located etc. One gotcha is "ghosted" files. i.e. whenever a file is changed using the SharePoint Designer the file is backed up to a database and from now on IIS will only use the file in the database, so there is no use changing the one in the file system.
To sum up:
In my humble opinion if you are making a site where uptime isn't that important and you can afford to make mistakes in production, SharePoint can be good enough with the designer. If you are making a CMS site where you need the code to go through multiple environments before it reaches production, (with continuous integration), I can think of no other .NET based CMS that does a worse job. You will spend a LOT of time grokking how to get the deployment routines to work for you, and you will spend a LOT of time with issues relating to "ghosted" files
Good luck.
63
Technet has a bunch of virtual labs for SharePoint products.
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
