I am referring the Alfresco docs and I have already gone through the Alfresco Web Quick Start. At the end of reading the docs I am still confuse that What is conceptual different between Afresco Web Editor (AWE) vs Alfresco Web Quick Start (WQS)? When should we use each of them? Any special use-case?
AWE is only a module used by WQS for in place editing of the articles.
For example, AWE does not know anything about collections, live site and editor site, publishing, navigations, etc...
The templates of an article in WQS are written using tags that AWE can interprets to show the editor form in the expected section of an article.
This article is the best guide to learn what you need to start developing with WCMQS. It has also some good graphs that describes how AWE is integrated in WCMQS.
Related
I has created eshop in shopify and I want to add a functionality ( with the framework .net ) in shopify but I don't know how....
I searched on the internet but I didn't find anything just I found this link from the ShopifySharp github but I didn't understand how to use it.
Who can help me?
https://github.com/nozzlegear/ShopifySharp
There are several possible ways to add functionalities to a Shopify shop depending on what you want to do.
They range from editing your shop's theme (mostly for simple needs) using html and/or js and/or and/or css and/or the liquid templating language (be careful though that any theme update may override your edits), to developing and hosting a custom app that would interact with your shop via a set of APIs (for more complex needs). Both techniques require a certain level of expertise (especially the later). See this very complete blog article for more info about how to build a Shopify app.
Basically you can build an app using any language and framework. The repo you found on Github looks like a C# SDK implementation of Shopify API. You are free to structure your app as you want provided you authenticate and communicate with Shopify using the possibilities offered by the API.
I'm working in a web application that has several areas of bussiness work. With time it's size has became a problem to develop on and to maintain.
I would like to break the web project into several sub-projects or libraries depending on a main root web project that has the common files to share (Masterpages, Resources, Css, etc...)
Ideally I would like to have some kind of injection that allows me to optionally publish that "components" or simply publish a customized variation, although it's configuration depended on after deploy DB setup.
I searched all over the web, reading all the pages related to multiple projects, dependency injection and composite apps that I could find, 'till I soften my head, but couldn't find anything really useful.
Major part of the writings where a theoretical approaches or unit testing applications (well, you can't make your desired app, but you still can unit test something else)
Other approaches simply don't work in VS2010 .Net 4.0
Can someone address me on a COMPLETE solution or an example? Or simply lets discuss.
We say that the solution has the following structure, with module contents already separated into directories:
Solution
L_ Datalayer library project
L_ Bussiness logic /common utils library project
L_ Web project
L_ Controls
L_ Images
L_ Css....
L_ Warehouse
L_ Sales
Masterpages
...
Warehouse and Sales contains pages related to the "module"
Thanks,
I post my progress in the subject.
As per suggestion of Steven I experimented further more using MEF. Due to the lack of documentation, specially for webforms, that was a pain in*. So far I managed to implement MEF in my solution and sucessfully inserted a plugin project visible for the main app.
Then loads the available plugins, through an interface that has the plugin name, the default page url and its order, picks all this data and render a menu tab. That part it's easy.
Clicking on a menu element must redirect to the main page of the plugin, which will render several menus for its pages contained (from another export interface)
I finally got an aspx page embedded as a resource in the plugin project. Where I'm currently stuck.
¿Is there any way to render a page embedded as a resorce on a libray using MEF or I'm forced to also use a VirtualPathProvider? ¿Hows specifically the statement to redirect to that page? I've tried several ways but no-one works (MEF and VirtualPathProvider)
I looked at zillion of articles that talk about it but all them end doing control rendering, not page. So frustrating.
Though it is not an answer to your question, I am adding it as answer due to length of my suggestion.
I suggest you look into the approach NopCommerce is following where they have extended over .net with their own framework, which supports Plugins and extensions to existing solutions. Though I definitely know that nopcommerce is an ecommerce solution but if you study it, you can modify it according to your business needs or at least it can give you a heads on for what you should adopt while designing your solution. Hope it helps.
I am developing a site (ASP.Net based) that, besides other features enables the users to blog as well. I am thinking of integrating BlogEngine.Net to my portal.
From whatever little I have analyzed, integrating at presentation layer will be far more challenging in comparison to doing so at business layer. That means (I guess) I will have to use the BlogEngine.Core.dll in my application.
I am looking for some sort of approval from the community, complimented with suggested do's and dont's. BTW, I find the business layer a bit intimidating (complex) as I want some basic & necessary features only.
you can check out http://www.ajaymatharu.com/integrating-blogengine-into-an-existing-site/
I recently did this for a client - note how I styled the blog to fit the main site design:
http://www.homenetdirect.com/
This was an ASP.NET 3.5 Web Application Project with master pages. I took one of the basic themes from BlogEngine that resembled what I was trying to get lookwise. Then I had all the elements that needed to be styled. Do the CSS gradually starting from the main container and work your way in (use Firefox dev toolbar). One more thing: I had to set up a subdomain for the blog - contrary to what a lot of people say, this will not hurt your SEO. SEO starts and ends with good content.
EDIT:
Creating themes for BlogEngine (Al Nyveldt's tutorials are worth watching):
http://www.nyveldt.com/blog/post/BlogEngineNET-Creating-Themes-Webcast.aspx
I integrated BlogEngine.NET 1.4 on my website. The result is exactly ONE web application (not a web site). However, the task wasn't an easy one as I had to change the source code of both the presentation layer and the core DLL to fit my needs. Now there's already version 1.6 and I guess, I'm gonna have to do same work again some time.
We've recently finished internationalizing a website and are ready to begin the, im sure, arduous task of localization / translation. The site is written in ASP.NET, and im looking for recommendations from people who have done it. CMS or Resource Files? If resource files, is there a recommended management tool? Budget, within reason, is not a factor.
Resource files for sure.
I recently finished a localized website and the tools in ASP.NET for localization are great.
Basically, you have two choices. Implicit or explicity localization. Implicit means the website reads the culture selection of the web browser and serves the correct language and explicit means the user chooses which language they want by clicking on flags or similar technique.
Everything I needed for the project was learned right here:
http://msdn.microsoft.com/en-us/library/fw69ke6f(VS.80).aspx
If there are business users who management content on the site then you'll need to think about a CMS.
If it's purely developer driven then resource files should be fine.
i have created a project in asp.net.now i want to implement asp.net administration tool in my project for user management.The tool works fine in a website ,but in a project it does not work.
Actually i have used the follows links to do this:-
http://msdn.microsoft.com/en-us/library/bb515342.aspx
When i implemented this walkthrough in the project, the Profile.aspx.vb shows errors.Means in this walkthrough it is specified that profilecommon will be formed dynamically.In website its working.But in project its shows 'ProfileCommon is not defined. What may me the reason?
It sounds like you want to implement your own version of the ASP.NET Web Site Administration Tool (WSAT) for use "inside of" your own website.
The walk-through that you link to is okay, however, it doesn't walk through creating anything that is particularly generic and can be simply "dropped in" to an existing web site.
I'd suggest looking at this tutorial:
Rolling Your Own Website Administration Tool
as a way of creating your own set of pages specifically for user/role/membership management. You can even download the code for the article if you don't want to re-type it all out yourself. Unfortunately, the code for this tool and in this article is in C#, however, the code is not especially complex and should be able to be easily converted to VB.NET using one of the many available code converter tools.
There is also this tutorial:
Users and Roles On The Production Website
which is VB-specific and should help with building your own WSAT-like tool.
Some time ago, on the CodePlex site, there was an ASP.NET WSAT Starter Kit project that also served the same purpose (and arguably improved on the "default" WSAT considerably), however, that project unfortunately no longer exists. After some searching however, it appears as though the code for this tool is still available, so you could perhaps take a look at that tool also (the code is in VB).
You can find that here:
ASP.Net WSAT (Web Site Administration) Starter Kit. What happened?
(check the very last post at the bottom of the page).