Am new to SharePoint but have better experience in asp.net web application development. I am using Visual Studio to development SharePoint application.
I have created two visual webparts - 1. StudentPersonalDetails: to add personal details of students and 2. StudentCourseDetails: to add course details of the student.When save is clicked in StudentPersonalDetails it adds the data to a list - ListPersonalDetails. When save is clicked in StudentCourseDetails, it should add data to the list - ListCourseDetails. ListCouseDetails contains StudentID which is to be passed from StudentPersonalDetails to StudentCourseDetails.
How can i do this? Am using Visual Studio 2010 for application development. Is a practice in SharePoint 2010 to use session variables, viewstate variables or querystring?
It looks like you are wanting to do web part communication. This functionality is available in SharePoint and you can see an example of doing this here.
http://msdn.microsoft.com/en-us/library/ff597538.aspx
Also you can see this option on web parts by clicking on the edit menu and there is an option for connect to on the web part options.
Here are some links; may be helpful to you. It is better to move this question to sharepoint.stackexchange.com
http://msdn.microsoft.com/en-us/vstudio/ff623014.aspx
http://blogs.msdn.com/b/bethmassi/archive/2010/01/28/creating-a-sharepoint-visual-web-part-using-visual-studio-2010.aspx
Video:
http://www.youtube.com/watch?v=mFHQYQIMVPk
http://blogs.msdn.com/b/bethmassi/archive/2010/01/28/creating-a-sharepoint-visual-web-part-using-visual-studio-2010.aspx
Related
I wanted to build a VB.net web application using MS Visual Studio 2015. Someone suggested me to create a Web API instead of MVC project if i'm also planning to create a mobile app later on. I may use angularjs in my project so controllers will surely be used, so what should i choose when creating the project in the first place?
Because when i created a web project: File=>New Project=>ASP.net Web Application=>Empty..there are no folders for Controllers, Model, etc. Do i have to create a Controller folder on my own?
Or should i do this: File=>New Project=>ASP.net Web Application=>Web API..? sorry if its a silly question. its just that i'm afraid that if i chose the wrong project now, it'll affect the development later on.
Answer to your question mainly depends on your choice and needs,
for example
In Case of an empty project as name defines you will have nothing else web.config.
Benefits of it:
here you can define, design your own structure. you can either make
it simple 3 tier or you can make it WEBAPI application. it's all up
to you.
however in the case of choosing Webapi template you will have a prebuilt structure which can help you out for initial understanding
https://docs.asp.net/en/latest/tutorials/first-web-api.html
benefits of it
You will get predefine template and structure.
you can utilize of webapi's which further isolate you backend logic from the frontend.
as you are also planning to create the mobile app. and using front end as angular, so in that case, webapi may come handy.
as the whole world is moving towards webapi, so i will recommend you to use it. please refer https://blogs.msdn.microsoft.com/martinkearn/2015/01/05/introduction-to-rest-and-net-web-api/
so down the line it all depend on you if you want to build you application for the stretch and take full control of it regarding structuring backend etc.. then go with empty else go with Microsoft pre-define template
Thanks,
Ajay Kotnala
I am trying to understand different artifacts around implementing Tridion XPM. Unfortunately I did not find any article that has answers to my questions.
For example Content delivery server (on WebSphere) can have four different applications, one for Content delivery(which handles publishing), one for web service (oData implementation), one for XPM (with Session preview) and the actual preview application. I am assuming we can merge one or more of these applications into one for a simple implementation (with one or two consuming websites).
My questions are:
How can we simplify the number of applications (WARs) to be made? Though I always prefer to keep the preview application separate from Tridion's framework. What are the benefits around Content Delivery session preview Web service as a standalone Java/JSP Web application Versus adding it to existing application?
How can I associate/integrate webservice(oData) to XPM or other common basic functionality like component linking?
For example if I publish a page with out enabling oData it will split tridion:ComponentLink tag where as if I enable it will split tcdl:Link tag. So I need to come up with custom class to read these tags? which eventually require adding Tridion framework in the preview application. (Assuming I did not include any Tridion framework in my preview to have a clean application dependency)
I looked at Tridion's live site for more information, but I could not find much useful info for my questions.
There's a LOT of questions right there, let's see what I can do here.
You will need 3 applications:
A Deployer (standard deployment configuration)
A Staging Website (with Tridion stack + XPM Filters + Ambient Framework)
A WebService app (OData + Ambient Framework)
XPM itself runs in the Content Manager Explorer, so it's not per se a separate app, it's an extension of the Tridion Content Manager.
If you want to have your staging separate from Tridion, then you will not be able to use "Session Preview", which in turn means you do not need OData. This however will revert back to the SiteEdit days whereby every change you do to pages requires the page to be republished (with Session Preview this is immediate).
You do NOT need to use OData for your Website in any way (unless you really want to). The WebService is there to support Session Preview only. I wrote down the interactions between XPM/CME/Staging site here and they're documented here.
If you publish tcdl:link code to OData, then just use TCDL/REL, Tridion will render it for you, you don't need to custom parse anything.
Hope this helps...
I need to generate reports from database (billing forms for example) from ASP.NET interface. So I'm wondering which approach is better : Use Crystal Reports, reports based on RDLC or SQL Reporting Services ? I need to create an interface, which allows user to select data and through pre-created report definition generate that report. I want to use ASP.NET with AJAX, so it will act as a real application, but with no need for installation - and this is primary requirement.
So, if somebody knows which technology suits best those requirements...I will be grateful :)
Personally I would go for DevExpress XtraReports.
I have used it in the past in both windows forms and web forms; it costs few hundreds of bucks but with the package you also get plenty of other UI controls, or you spend less and only buy XtraReports. It pays off in a flash, main advantages in my opinion are:
each report can be designed with a Visual Studio integrated designer and becomes a simple c# class, easy to instantiate and use, no magic and no external report definitions, all pure 100% .NET code;
end user designed is royalty free and users are amazed by the power and quality of the designer, with Ribbon or classic UI, plenty of features;
so many out of the box zero coding ready to use features like print preview, export to excel, pdf etc...
Disclaimer: I do not work for DevExpress, I am not paid by them, simply I am a satisfied customer and used their products before with joy and good results, we are now in the process of starting a major MVC application development in my company and we are buying licenses of their DXperience Enterprise subscription these days.
you are free to also evaluate or test Crystal Reports or similar reporting solutions offered by ActiveReports, Telerik etc, I can only speak about XtraReports because I used it a lot, Crystal I used in the past with Visual Studio 2003 but I was not so impressed by the designer and deployment was really a mess in windows forms... always missing some files and having errors on client machines...
I would suggest taking a look at ActiveReports 6. It provides great features and allows you to make almost unlimited customization to your report. For ASP.NET you can either opt for the standard edition which allows you to custom export your reports to different formats like PDF, Excel etc and display them to the users.
The professional edition provides you a webviewer control which allows you to display reports directly on the viewer and the user has the option to chose from PDF, HTML and FlashViewer format. In addition to this it also provides a silverlight based viewer control.
You may also want to check the blogs and the forums just in case you want to get more information about the product.
Thanks,
Sankalp (GrapeCity)
Don't miss to take a look into List & Label, too.
We've done some good projects with it!
We use SQL Server Reporting services, it has a visual studio based designer, and it's free. The distribution is a little tricky - If your clients already have SQL Server installed, then there is a a good chance they will have the reporting framework installed. Otherwise you can get just about distribute the dll's with your application - although this takes a bit of digging.
I am wanting to display an Excel 2010 document in an asp.net web application. This document uses the new slicer functionality which I want to be available to the user.
I know that Excel 2010 docs can be used within SharePoint by inserting a web part which uses Excel services.
But can it be achieved without SharePoint ? Or can it be achieved using the the Excel services API to get the document from SharePoint and then somehow get it to the browser in .net?
Thanks,
Tom.
I am not familiar with the Slicer functionality but.... Excel cells are available via a REST interface within SharePoint 2010 (not 2007). That may help you get to the data you want to expose.
More information on the Excel and Rest with SharePoint 2010 here.
From a non SharePoint perspective, the Skydrive based Web Office apps have Excel functionality. It is possible you may be able to impersonate a user, send a HTTP request to try and bring back the Excel data for display. You could possibly use an IFrame for display also. Having said that, I have never tried it and not sure how well it would work.
Ok so we have an upcoming development that will involve a level of off line processing of dynamic forms. Here's what we have to do:
Create a asp.net web application whereby users can download dynamic forms, fill them in then upload them to be published.
We also have a windows mobile application that will do something similar.
The forms will requires images to be selected for uploading when publishing.
Upon publishing the completed form certain server side validation needs to occur which may trigger additional work to be done i.e. send out emails or update a database etc.
From what I know of InfoPoint (which is next to nothing) it seems like it may be a nice fit. I know its quite highly tied to SharePoint (which again I know nothing about), but can it be used without a SharePoint instance?
Either way, I am just firstly looking for validation that InfoPath is a good fit for what I describe. If it is the I am also after some good online resources.
Thanks in advance, Chris.
I don't think that there is an InfoPath client for mobile devices. What you would want to do is use Forms Server (comes with SharePoint 2007 Enterprise edition) to render InfoPath forms as aspx to the mobile device.
Everything else you describe could be done with straight ASP.NET and the InfoPath client. The mobile piece sounds like it will require SharePoint (for rendering the InfoPath forms as aspx).
See this blog post on using Infopath forms on mobile devices: http://blogs.technet.com/vik/archive/2008/02/25/filling-out-infopath-forms-on-windows-mobile-devices.aspx
Also the Formotus solution may work for you: http://www.formotus.com/
Before delving into whether or not InfoPath (+ SharePoint) is the right solution, what's the reason for not using ASP.NET with which I assume you are familiar? While InfoPath + SharePoint is sexy and hot right now, the learning curve is very high.
Back to InfoPath, I don't believe InfoPath supports uploading files. At least not out of the box. So if having your users upload images is a requirement, I'll say infoPath is out. Apart from that, InfoPath, with the addition of SharePoint Forms Services and workflow, can be used to accomplish what you want. I just wonder what the cost would be versus using straight up ASP.NET.