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).
Related
I'm going crazy because I can't find the ASP.NET configuration tab in Visual Studio 2017.
I'm following Microsofts ASP.NET tutorial on how to create a login page with members.
This is what the tutorial tells me.
And this is what my menu looks like.
Please help me. I've been looking after it for an hour now without any luck.
Link to the relevant chapter.
This menu item was removed some time ago (VS2013 or VS2015, I can't remember). It's unfortunate that the documentation hasn't been updated.
Anyway, you should check out ASP.NET Identity instead. It's now preferred over the old Membership provider model you're looking at. Give it a go at asp.net/identity
I assume you were on this page, yes? If you click the other versions link, you can see its meant for Visual Studio 2010. Nice of them to make that obvious, eh? Anywho, if you want built in authentication you can still use it, you just have to pick the Individual Accounts option for authentication when creating an account. This is not using the old school Membership Provider though, as that is outdated. Detailed instructions can be found here.
If you still really really want the old MembershipProvider, I would suggest just downloading Visual Studio 2010 from here and going to town. Enjoy!
Has there ever been a more confusing/difficult time to be a web developer using the Microsoft stack? That's not really my question... I know that the answer is a categorical no. :)
The single page app template that comes with VS 2013 is deplorable.
I've been working on building up a similar project template that uses Angular JS on the client, but I'm starting to spin my wheels a bit porting over the external (openId/oauth) login features.
I believe this is because of the lack of good, single-point-of-truth, and current documentation for Katana's auth/security bits and also because of how unreadable the client side code is in the S.P.A. template in visual studio 2013.
I know that I can get through it, but while I'm struggling with it, I'm wondering:
Are there any good community provided project templates or example code bases in existence that use .NET 4.5 (MVC5/Web Api 2), Angular JS, the new ASP.NET Identity stuff, and the Katana packages?
There's HotTowel.Angular, but it takes no stance on security. Besides, it's a Nuget package, which can't or shouldn't dictate as much as a proper project template can.
I agree with your observations. I have found the following setup that seems to meet your requirements and I think works very well (I don't have a template), I would suggest the following:
Create an empty WebApi2 project and adopt authentication/authorization depicted here
Use a regular index.html in the base directory as a launching point for your angular application. You can either maintain your client packages with nuget, npm, or bower.
Use whatever technique you like for organization of client code.
Personally, I would create 3 projects, One for client code, (mydomain.com) One for your api (api.mydomain.com) and one for your Model/Repository/Data Access layer.
update
Here is an open-source project that might be what you're looking for!
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 was recently asked to create a web page using a static website generator, like Jekyll. My question is this:
How does this differ from just creating a website using HTML or writing the page as an ASP.net project in Visual Studio?
How does it work on the server?
What are some concerns I should have?
I'm a .net guy, so I would like to be able to create this in visual studio, if possible.
Here are some advantages and disadvantages that came to my mind:
Advantages
can be deployed on every server, as it's just static html
has partials, that can be reused, in contrast to normal html, where you have to code/copy paste every thing
you can still code in an IDE
a non developer can edit code (sometimes at least)
Disadvantages
the template language is limited and sometimes a bit awkward/needs to get used to
you have something new in your environment, which has additional costs (more than one developer needs to know how to build the site, ...)
If you know your current toolkit well and you do not have a problem hosting another ASP.net project on your server, I do not see the need for you to introduce another tool in your tool chain.
If you want to do something, where users can generate content - like github does on the github pages - this is something you might consider.
As for Jekyll, we tried it on one project and being devs, who like to code, we ran into it's limitations quite early. You can work around this, but if you know a programming language you will be faster. It was still fascinating, how far we were able to go with just using Jekyll
With ASP.NET pages exist throughout the life cycle of the page, and able to work with request and session context. See this article asp.net page life cycle
HTML pages are static and you can not access any variable that is on the server.
I recommend you follow the step by step this link to go to just understand how to develop ASP.NET http://www.asp.net/get-started
I hope that helped
Vicente
I need to add a gallery to my website, to show screen shots of websites and applications.
I run IIS.
I'm looking for something that is fairly self-contained and ready to integrate without a lot of work. I'd like to through a bunch of images in a directory and let it go.
I would love some nice effects for browsing the gallery.
What would you suggest?
You might want to look at nGallery for ASP.NET 2.0. I've support an application that uses an older version of this. No experience with this particular version, though.
Consider Gallery Server Pro (www.galleryserverpro.com). It is a free open source web gallery based on ASP.NET and has been around for several years. It is easy to integrate into an existing site by using the self-contained ascx user control.
Disclaimer: I am the Creator and Lead Developer.