I have been in search for a Web Developer Designation hierarchy to implement in the Web Development Department in the company that I work.
for eg: Associate Web Developer -> Web Developer -> Senior Web Developer -> what next?
Please Suggest..!!
How about 'Web Architect'?
Around here, the next step up from 'Senior Developer' is usually 'Architect', if that is what the individual is interested in.
Related
We are in the Design phase of a Project Management system, and we have 2 technical approaches to follow:-
SharePoint as the Back-end + Power Apps & Power Automate
SQL server as the Back-end + ASP.NET Core MVC
Now at the beginning, I thought that the requirements can be achieved using the first approach (SharePoint). but the customer start giving us some requirements which i do not think SharePoint will support. one of those requirements are:-
We will have 2 SharePoint lists; Projects + Project Personnel.
Project will have those main fields:-
ID
Project Title
Description
Project Personnel
ID
UserName
Role (Engineer, PM, Data Entry, Senior Engineer)
ProjectID (reference to the Project list)
Now in our case we have those business rules:-
Only users who are defined inside the IT Admins Office 365 group can add projects (this is achievable in SharePoint by setting the list permissions)
User inside the IT Admins Office 365 group can add PM and other Personnel roles (this is achievable in SharePoint by setting the list permissions)
PM defined inside a Project can add other users to the project, but can not add others as PM. and PM defined inside a project can not add other users to other projects.
so not sure if requirement 3 can be achieved in SharePoint? i know i can do this inside Power Apps, but if a PM user access the Project Personal SharePoint list directly the PM can add users to any project.. now the customer want us to provide a secure solution, so we need to secure the back end. so i do not think SharePoint will achieve this. while if we use SQL we can secure the back-end using a server-side language such as ASP.net core mvc, and we can prevent users (PM for example) from directly accessing the SQL server databases and only allow direct access to the service account.. so can anyone advice if we should use SQL instead of SharePoint ? to implement our requirements in a secure way?
Thanks
I have a simple 2-page ASP.NET application that is hosted as a 'azure website'. I want to make this application secure by integrating with my company's ADFS. What is the simplest way to integrate this app with ADFS. I don't want to go through ACS if I don't have to. It looks like it is possible to make the asp.net app talk to adfs directly using WIF.
Can someone confirm if this will work and share any pointers to get this working?
You are spot-on about not considering ACS.
The simplest way is to just let the tooling in Visual Studio 2013 wire it up for you.
Create a new ASP.NET Web Application project and in the new project dialog, click on the Change Authentication button.
Next, select the Organizational Accounts radio button, choose On-Premises in the drop-down, and fill in your On-Premises Authority and App ID URI.
Vittorio blogged about the full experience here if you need more detail.
You will have to substitute in the correct URL's for your Azure Website, but this should get you going in the right direction.
I would like to what is the differece between the webapplication and the website.
Any suggestions will be greatly appreciated!
Yes there is difference between web-app projects and website projects.
Text from the MSDN :
In Visual Studio you can create Web application
projects or Web site projects. Each type of project has advantages and
disadvantages, and it is helpful to understand the differences between
them in order to select the best project type for your needs. You must
select the appropriate project type before you create a project,
because it is not practical to convert from one project type to the
other.
In layman language:
Web application:
If you can think of a site where you create an account, log in, and conduct some actual business, it’s probably a web application
So a web application is a web site that DOES something other than display content to the user.
It’s intended for user interactions and transactions, performing actual business functions, and not simply displaying information to users.
Some example of web application
GMail,Facebook,Ebay,Twitter,YouTube
Web site:
Web site usually use for dispaly information .They have less or no interaction with users, so we can say Websites are informational by neture.
Some example of web site
Nokia.com,Songspk
For development point of view
The Microsoft best described this on there website here here
Please take a look on following table-
We currently have a product that uses Sharepoint and a number different Web Part libraries to display realtime data to customers. The way this has been set up is that each customer has a custom login (Active Directory), a custom site with their specific data hooked up in the web parts. That means for every customer we have a completely separate site. Eg:
Customer 1 -> www.site.com/sites/customer1
Customer 2 -> www.site.com/sites/customer2
Customer X -> www.site.com/sites/customerX
As you can imagine, this is impossible to maintain as any small change that we make has to be manually propagated across all of the site, a task that has become impossible.
We are also developing separate ASP.NET MVC application that live on the same server under their own Virtual Directories Eg. www.site.com/App1/
I've been tasked with investigating how to best redesign the system to provide a more integrated and "application platform" type architecture.
Personally I would love to just ditch the Sharepoint as I think we are using it incorrectly (not as a CMS at all), but my manager wants to keep the Excel Services for customers who pay extra (a customising service).
We currently embed the MVC applications in Sharepoint using the Page Viewer Web Part, but this gives us less control over the layout of these applications
My next thought was to have a standard ASP.NET masterpage across all MVC sites and sharepoint so that they look the same, whilst still providing the functionality required, but investigation and testing seemed to be that Sharepoint master pages are horrible beasts that barely resemble a clean master page.
Basically I'm stumped, and I'm getting a little disheartened about Sharepoint and it's god awfullness.
Does anyone have any experience with this or could provide some ideas/tips?
Very much appreciated.
CodePlex - SharePointMVC
A helper project for hosting asp.mvc content inside SharePoint.
We run multiple apps to provide services to our members at our organization
1. DotNetNuke as CMS
2. Classic ASP custom app for membership management and event management
3. ASP.NET app for providing online learning
4. Wordpress blog
Can somebody please suggest a way to enable Single Sign On in this kind of an environment.
I am looking for a solution which would enable adding any kind of application easily to the SSO in the future.
We host most of the apps, but there are some being hosted outside our environment as well.
All members are customers in different locations.
THanks
You could use Live ID:
Windows Live ID with dotnetnuke:
http://www.datasprings.com/Resources/ArticlesInformation/DotNetNukewWindowsLiveAuthentication/tabid/828/language/en-US/Default.aspx
Windows Live ID with wordpress:
http://social.msdn.microsoft.com/forums/en-US/wliddev/thread/a34d1585-e602-4519-858c-0bb5ae02856d/
You could also use Open ID, the same as stackoverflow.
Live ID will be compatible with Open ID:
http://winliveid.spaces.live.com/
Have not been able to find a reference to use of Live ID with classic ASP.
You can use Windows Live ID to identify people with it.