We want to use Infopath forms in stand alone application. How can we use Infopath forms in standalone application?
I assume that you mean without connecting to Sharepoint. Then yes you can use it as a standalone application.
Edit
My assumtion was that standalone meant using infopath client by itself to create the XML datafiles.
If I understand correctly you are wanting to use Infopath Form Services to deliver web based forms. In that scenario, no you will not be able to use it without Sharepoint as Infopath Form Services is built on top of Sharepoint 2007.
It is possible to convert an Infopath form to be viewable on the web however. To do this you will need to be familiar with XML and XSL and only use browser compatible controls. The Infopath XSN file is really a CAB file that contains an the View (XSL), data (XML), schema (XSD) and other files. to make the form viewable on the web means editing the xml template to point to the XSL view rather than opening up in Infopath.
Hope that helps.
Install InfoPath designer to design client based forms and install InfoPath Viewer on client machines to work on published forms.
Related
I need to integrate ASP.NET into an existing Flash site. The site is heavily laden with Flash and needs to communicate with a SQL Server database. I want to use ASP.NET SQLDataSource for this purpose. Given that I need to integrate the two technologies for one web page on the site, do I need to make the site fully ASP.NET with embedded Flash objects? Or, can I just add a single ASPX page to the site that contains the web.config and connection string to SQL Server?
Thanks much for your help and guidance.
What exactly are you trying to accomplish? Does the Flash need to access the SQL server through .NET? How does it need to interact? If the Flash component just needs to access data, I'd recommend skipping the .aspx part and just having an HttpHandler that acts as a gateway to the database. Is Flash JSON-friendly? If so then it would be fairly easy to just pass relevant arguments to the handler (maybe just URL values) and have it serialize a response.
In our windows application, we used crystal reports. If a customer needed a custom report, we could create it and then send them the rpt file. The customer would then simply add the report file to a custom folder, and could access it directly from our application.
Using a web app, how is this possible. It seems like anything created, using ssrs, crystal, or even telerik reporting must be embedded.
What are some methods for providing custom reports to users of an asp.net web application?
If your users need lots of custom reports, just give them access directly to ssrs. you can control security, permissions, and simply upload as many custom reports as they need and the ssrs gui would let them access it
Is there any way that I can use SharePoint document library and document sharing functionality from an ASP.NET page?
There's 3 ways you can have your standalone ASP.NET (standalone meaning not integrated into sharepoint) interact with sharepoint.
1 using the SharePoint object model (sharepoint APi dll's). This way allows you to control every part of how your ASP.NET site interacts with SharePoint (document security etc.) The major drawback is that you ASP.NET site needs to be running on the SAME SERVER as SharePoint (or if sharepoint is used in a farm any machine that is running sharepoint in that farm). Simply including the SharePoint DLL's will NOT work when run on any other machine (even when that machine also has sharepoint installed but is not part of the farm you want to communicate with!)
2 Web Services. These OOTB services can be used from anywhere but are not very extensive functionality wise. They allow you to perform a lot of actions and retrieve a lot of data, but when it comes to more finegrained control they just don't cut it. It might be enough for what you want to do though.
3 Use web services and create your own webservice that is deployed to sharepoint for any tasks not doable with the OOTB services. This requires access to the sharepoint machine in the form of deploying custom code / assemblies though.
I assume that your asp.net application is running on another server because if thats not the case the it would probably be easiest to just use the SharePoint functionality directly and maybe include your app into SharePoint
SharePoint exposes a lot of it's functionality through Web Services, so you can get, add, delete and update information through these.
You can include any SharePoint page into a page in another portal using an IFrame. The main issue there is the fact that you will get the MOSS navigation in that IFrame, which typically is not desired. To overcome that, you can create a special MOSS page that hides all those elements and show just the element you want to expose. To accomplish that, you can create a “minimal” master page and a simple layout with a single web part zone.
Is it possible to use SSRS for reports in an ASP.NET 1.1 application? Is there a report viewer control for ASP.NET 1.1? If not is there any workaround for this?
One way you can get around it is to use the querystring commands that Reporting Services makes available and serve up the reports in PDF format (or in any of the other deliverable formats to the end user).
Reporting Services itself requires .NET 2.0 to run on its own, so there is no actual controller for displaying the reports live on a website that is only .NET 1.1
Edit: Here is the MSDN information concerning URL Access.
http://msdn.microsoft.com/en-us/library/ms153586.aspx
http://msdn.microsoft.com/en-us/library/ms153563.aspx
I have used the report viewer control, but have not found it very useful the majority of the time. Depending on what you are trying to accomplish, you can access the reports directly via a URL. You can even do this with passing parameters to the report.
For example...
http://reports.mycompany.com/reportserver?%2fMyCompany%2fProject+Folder%2fReportName&EndDate=2/21/2009&BeginDate=2/15/2009&rs%3aParameterLanguage=en-US&rc:parameters=true
The other option that is available is to use the web service that is part of reporting services. You can then render back the bytes of the report in different formats (PDF, word, Excel...) and output those to the user for download. I can give you more information on the web service if that is the route you are looking at...
You can access the Report Server through the web service interface from asp.net 1.1. Add a web reference to your project and then call the various web methods exposed by the report server to render your reports in one of the available formats. For example, if you render the report in HTML format, you can inject the HTML into a Literal control for display on your web page. You don't get the advantage of the report viewer's interface for selecting parameter values, paging and exporting, but it should be possible to create a page that mimics those functions.
I'm looking at building some web user controls with an eye toward re-use, but I can't seem to add a Web User Control in my class library in VS2008. Is there a way to work around this problem, or is there a better approach to creating reusable controls?
You can create either Web User Controls or Web Custom Controls that encapsulate the functionality you need. The main difference between the two controls lies in ease of creation vs. ease of use at design time.
You should maybe consider creating a Web Custom Control library. There is a walkthrough for creating a web custom control using the Web Control Library template.
According to the MSDN article "Recommendations for Web User Controls vs. Web Custom Controls" these are the differences between the two types of controls:
Web user controls are easy to make,
but they can be less convenient to use
in advanced scenarios. You develop Web
user controls almost exactly the same
way that you develop Web Forms pages.
Like Web Forms, user controls can be
created in the visual designer, they
can be written with code separated
from the HTML, and they can handle
execution events.
However, because Web
user controls are compiled dynamically
at run time they cannot be added to
the Toolbox, and they are represented
by a simple placeholder glyph when
added to a page. This makes Web user
controls harder to use if you are
accustomed to full Visual Studio .NET
design-time support, including the
Properties window and Design view
previews.
Also, the only way to share
the user control between applications
is to put a separate copy in each
application, which takes more
maintenance if you make changes to the
control.
Web custom controls are compiled code,
which makes them easier to use but
more difficult to create; Web custom
controls must be authored in code.
Once you have created the control,
however, you can add it to the Toolbox
and display it in a visual designer
with full Properties window support
and all the other design-time features
of ASP.NET server controls.
In addition, you can install a single
copy of the Web custom control in the
global assembly cache and share it
between applications, which makes
maintenance easier. For more
information see global assembly cache.
Follow the following steps (from this post by Phil Haacked):
Close VS.NET 2005.
Open the directory C**:\Program Files\Microsoft Visual Studio 8\Web\WebNewFileItems\CSharp** (assuming a default installation of VS.NET).
Open the CSharpItems.vsdir file in Notepad. Select the text and copy it to the clipboard.
Now open up the file C:\Program Files\Microsoft Visual Studio 8\VC#\CSharpProjectItems\CSharpItems.vsdir and paste the contents of the clipboard underneath the existing text.
Now copy the contents of C:\Program Files\Microsoft Visual Studio 8\Web\WebNewFileItems\CSharp (excluding CSharpItems.vsdir) into the folder C:\Program Files\Microsoft Visual Studio 8\VC#\CSharpProjectItems.
Now “Web User Control” should be an option when you select Add | New Item.
Reference: http://haacked.com/archive/2006/02/07/addingwebusercontroltoaclasslibraryinvs.net2005.aspx
As platte's link mentions, if you're going for reuse then Web User Controls aren't very good. The ascx file has to be manually copied to every project you want to use them in, or you have to hack your way around that.
It's better to use System.Web.UI.WebControls.WebControl which is what you get when you add an "ASP.NET Server Control". These are designed for reuse. If one of the existing framework controls fits the bill for the most part and you just need to extend the functionality of it, then add an "ASP.NET Server Control" and change it to inherit from Panel or Menu or whatever.
If you're still determined to get reusable Web User Controls to work, then this article by The Gu should set you on the right path.
There is a project template called "ASP.NET Server Control" that I assume you can use...
--larsw
You can do anything in a class library.
Add reference to System.Web
Create your new Control class that inherits
from WebControl or HtmlControl or
whatever.
That's it. You now have a reusable control for ASP.NET.
You could do some special things like add attributes to your class and properties, but they are really not needed.
[DefaultProperty("Text")]
[Category("...")]
[DefaultValue("")]
You could using virtual path providers but you you should consider whether it really is worth your wile. Consider this codeproject article on the subject.