Navigation

Search

Categories

On this page

1st look at the Asp.Net MVC Framework
Differentiating content by user privileges in Sharepoint 2007
Using MySQL with asp.net for authentication/authorization
Login Page loses styles when using Forms authentication

Archive

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 22
This Year: 12
This Month: 0
This Week: 0
Comments: 7

Sign In

 Monday, December 17, 2007
Monday, December 17, 2007 1:47:27 PM (Mountain Standard Time, UTC-07:00) ( asp.net | MVC )
 Ok!! So everbody and their mother have already blogged about the new MVC Framework released with Asp.Net 3.5 Extensions preview 1 week ago, but i just got time to try it out. Its pretty different from the WebForms model, and is not meant to replace it in any way. Its an alternative that promotes test driven design and makes it easy to unit test your code. As per ScottGu, it enforces a clear separation of concerns within applications. In other words, it makes it harder for the developer to make bad design decisions, because it encourages you to keep your layout (view) separate from the data access code (model) and business logic (controller). Also, the URLs in an MVC point to the Controller and not to the view, so it gives you much more control over the URLs in your application. You also do not have the file extensions as part of the url by default, since you are pointing to the Controller class, and you can specify the method (ControllerAction) to call along with the parameters in the URL itself.  The  controller invokes the appropriate view which renders the html.
 
 To learn more about Asp.Net MVC framework, check out the following resources:
http://www.hanselman.com/blog/ScottGuMVCPresentationAndScottHaScreencastFromALTNETConference.aspx
MVC Part1
MVC Part2
MVC Part3
MVC Part4

Its quite a handful for a 1 week old technology preview framework, isn't it!!

-Latish Sehgal

 Thursday, December 13, 2007
Thursday, December 13, 2007 4:46:07 PM (Mountain Standard Time, UTC-07:00) ( Sharepoint )
 Sharepoint 2007 allows user targeting at the individual web part level. You can control what each user sees by default by enabling audience targeting on the control in its Settings, and then configuring the user groups that should see the web part under Advanced 'Settings->Target Audiences' .


You should remember though, that this only removes the control from the default view, and can still be accessed via the 'View All Site Content' link on the site. To completely remove access to a control for a user group, you should also configure the 'Permissions for the List' under 'Settings->Permissions'.

-Latish Sehgal

 Wednesday, December 12, 2007
Wednesday, December 12, 2007 11:55:45 AM (Mountain Standard Time, UTC-07:00) ( asp.net | authentication | authorization | mysql )

MySQL database is a good option for projects that need large stable databases but cannot afford the Oracle or MSSQL price tag. The provider model in Asp.Net 2.0 allows us to use MySql with plenty of Out of the Box functionality. When using Forms Authentication, you can just configure the application to use the MySQL provider, and then use the ASP.NET Web Site Administration tool to manage users and roles in your application.

1. Make sure you have installed the latest version of MySQL Connector/Net. This also adds an entry each to the membership and rolemanager providers in the machine.config files behind the scenes.
2. Open the Asp.Net Web Site Administration page, go to  'Provider ' tab and click on "Select a different provider for each feature (advanced)".
3. Select ' ' as the Membership Provider, and ' ' as the Role Provider.


4. Add the connectionstring to your MySQL server under the name 'LocalMySQLServer'.
        <remove name="LocalMySqlServer"/>
        <add name="LocalMySqlServer" connectionString="server=localhost;database=mbs;uid=root;pwd=mbs"/>

5. Goto 'Security' tab and manage your users and roles.

 Saturday, December 08, 2007
Saturday, December 08, 2007 5:24:47 PM (Mountain Standard Time, UTC-07:00) ( asp.net | login | stylesheet )
One of my colleagues faced this problem recently while working on a new asp.net site, where his login page was not rendering as per the default stylesheet whereas all the pages displayed fine once the user logged in. When i looked at his web.config file, i saw that anonymous access was blocked to all resources on the site, and adding an <location> element allowing anonymous access to the images and stylesheets folder fixed the issue.
It looks something like

<location path="img">
     <system.web>
            <authorization>
                    <allow users="*"/>
           </authorization>
    </system.web>
</location>


-Latish Sehgal