MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Merchanse Store

  Asked By: Anila    Date: Aug 10    Category: MOSS    Views: 636

This is a simple ASP.Net using C# built on the Ajax extensions for
the 2.0 Framework and the PayPal dll's. It use a SQL Server
database. Again, it is a very simple application:
- the take Conferences Registation and purchase a product
- validates with some Ajax and validation controls
- stores that attendee info into SQL tables
- creates a PalPay button with the requested information as a form
- after choosing to pay by PalPay, it sends the form to PayPal
- once PayPal completes the transaction, it send a tranaction number
back to a our url
- then we use the PayPal API's for generate and invoice and confirm
- we also send an smtp email confirming the registration success
- last, we use the ASP Gridview bound to SQL Server to display
Conference Attendees and schedules.
- and we can easily use Reporting Services to verify attendee,
payment, etc.

We would like to use the same concept to also add merchanse to the
site. However, now we have install MOSS and would like to do this in
SharePoint. Is it possible? Would it take a long time to build such
an application? Or is it better just to integrate / incorporate this
app into SP? If the later, will intregrating the app use the SP
common look and feel, such as, master pages.



8 Answers Found

Answer #1    Answered By: Himanta Barthakur     Answered On: Aug 10

ASP.NET apps can be used within MOSS, most times with little/no
modification. From your description it doesn't sounds like there's a
compelling reason to re-write this specifically for MOSS.

Answer #2    Answered By: Mansi Revenkar     Answered On: Aug 10

What method of ASP.NET use are you referring to? I've read lots of advice on
web part pages, links, user controls -> web parts, etc. but still don't
understand what the rules or guidelines are for this. It would be nice if
someone could provide a concise summary of the methods available and their
relative advantages and disadvantages.

Answer #3    Answered By: Lizette Mcconnell     Answered On: Aug 10

MOSS is built  on ASP.NET, and can be used to host normal .aspx pages  in
addition to the SharePoint-specific pages, etc you see documented.
There are a few restrictions on *where* you can do custom .aspx pages
though (especially those with code). Generally speaking, if you deploy
to the _layouts folder things should just work.

Answer #4    Answered By: Rosanna Parrish     Answered On: Aug 10

Does this method provide the SharePoint security context, or do I need to
establish an alternate means of authentication?

Answer #5    Answered By: Kalash Karmakar     Answered On: Aug 10

If you deploy to _layouts, yes, it does.

Answer #6    Answered By: Mauricio Tanner     Answered On: Aug 10

From your input, forums and other messages from
MVP, I have three options, which at a standstill on how to start. They are:

1. Web Part pages  instead of ASPX pages. You could pre-configure the web
parts on the page, whether you place them in web part zones or not.

2. If you cannot factor the app  down into web parts, you could factor it
into server  controls and place them on a standard content page referencing the
default master  page.

3. Finally, follow Andrew Connell's chapter on Incorporating ASP.Net 2.0
Applications -

What would your votes be??? Or any other info  you may have to offer.

Answer #7    Answered By: Gina Freeman     Answered On: Aug 10

#1 is the most work, but is the right way to do it. If you can't do #1, you
won't be able to do #2 and vice-versa. #1 would be preferable to #2. #3 is
easier than #1, but doesn't provide a platform for future expansion and growth
of the app. If you just need to port it and never upgrade then do #3, otherwise
I would take the time  to refactor and do #1.

There are two other options also. One is to run the app  as it is in a Virtual
Directory under the SharePoint Web Application. Easier than either #1 or #3,
but provides less integration with SharePoint. Two is to run the app inside a
Page Viewer web part. This is essentially an iFrame inside SharePoint. It
makes it look like the app is inside SharePoint even though it isn't. It's the
easiest method of all, but isn't good where performance is an issue.

Answer #8    Answered By: Tyrell Nash     Answered On: Aug 10

This was a very difficult decision, since I'm
mainly an ASP.Net developer. I'll start with the 1st approach and see how it
works. At least it would be an excellent learning experience.

Didn't find what you were looking for? Find more on Merchanse Store Or get search suggestion and latest updates.