on codeplex: http://1code.codeplex.com/
All-In-One Windows Forms Code Samples
All-In-One WPF Code Samples
All-In-One Windows Azure Code Samples
All-In-One Silverlight Code Samples
All-In-One ASP.NET Code Samples
All-In-One COM Code Samples
All-In-One Data Platform Code Samples
All-In-One Office Development Code Samples
All-In-One Interop and Fusion Code Samples
All-In-One Windows UI Code Samples
All-In-One Visual Studio Extensibility Code Samples
Friday, November 26, 2010
All-In-One Overview
at
5:14 PM
0
comments
Posted by
roni schuetz
Labels: links
Monday, November 08, 2010
writing windows shell extension
Part 1: http://blogs.msdn.com/b/codefx/archive/2010/09/14/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-1.aspx
Part 2: http://blogs.msdn.com/b/codefx/archive/2010/10/10/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-2.aspx?wa=wsignin1.0
Part 3: http://blogs.msdn.com/b/codefx/archive/2010/11/07/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-3-thumbnail-handler.aspx
at
8:26 AM
0
comments
Posted by
roni schuetz
Labels: .net 4, links, Windows Shell
Tuesday, September 08, 2009
Wednesday, June 17, 2009
A BuildProvider to simplify your ASP.NET MVC Action Links
checkout the following links from David Ebbo's blog:
at
5:56 PM
0
comments
Posted by
roni schuetz
Labels: asp.net mvc, links
Monday, January 05, 2009
jQuery - VS 2008 and Intellisense
Steps to Enable jQuery Intellisense in VS 2008
Step 1: Install VS 2008 SP1
Link: http://msdn.microsoft.com/en-us/vstudio/cc533448.aspx
Step 2: Install VS 2008 Patch KB958502 to Support "-vsdoc.js" Intellisense Files
Link: http://code.msdn.microsoft.com/KB958502/Release/ProjectReleases.aspx?ReleaseId=1736
Step 3: Download the jQuery-vsdoc.js file
Link: http://docs.jquery.com/Downloading_jQuery#Download_jQuery
full story with details can be found here:
http://weblogs.asp.net/scottgu/archive/2008/11/21/jquery-intellisense-in-vs-2008.aspx
at
1:20 PM
0
comments
Posted by
roni schuetz
Labels: jQuery, links, visual studio
Tuesday, December 30, 2008
Must see JQuery Example - amazing
at
10:54 PM
0
comments
Posted by
roni schuetz
Labels: links
Sunday, December 28, 2008
ASP.NET MVC Linklist
- http://blog.wekeroad.com/
- Exploring System.Web.Routing
- Setting up authentication in asp.net MVC
- Using System.Web.Abstractions in Your WebForms Apps
- ASP.NET MVC Request Flow
- Hierarchical Treeview with ASP.NET MVC & jQuery
- ASP.NET MVC Tip #1 - Accessing TempData from a ViewUserControl
- ASP.NET MVC Tip #2 - Redirecting to another action and passing information to it
- ASP.NET MVC Tip # 3 - Getting an Absolute Url Using an Extension Method
- ASP.NET MVC Tip #4 - Handling Multiple Form Actions on One View
- ASP.NET MVC Tip #5 - Submitting an AJAX Form with jQuery
- ASP.NET MVC Tip #6 - Code Snippets for Quickly Testing Routes
- ASP.NET MVC Tip # 7 - Using a CAPTCHA with MVC (http://www.coderjournal.com/2008/03/aspnet-mvc-captcha/)
- Using the ComponentController in ASP.NET MVC CTP 2
- Fluent Filters, IQueryable and Linq To Sql for Easy Data Access
- HowTo: ASP.NET Chart Controls mit ASP.NET MVC nutzen
- HowTo: ASP.NET MVC Projekt erstellen (erster Einstieg)
- HowTo: ASP.NET MVC - Was ist es und warum sollte man es sich anschauen?
- LINQ to MSI - Part 0 - Introduction
- Linq to SQL Wish List
- # 7 - (re)Creating your DB with Linq’s DataContext for testing
- TDD Tips: Test Naming Conventions & Guidelines
- # 8 - Introduction to Mocking with Moq
- 3 mistakes to avoid when using jQuery with ASP.NET AJAX
- Implementing the Repository Pattern with Linq-to-Sql
- Mocking LINQ to SQL DataContext
- Code Generation Tool (SqlMetal.exe)
- More In LINQ to SQL with the Repository Pattern
- LINQ to SQL - Implementing the Repository pattern
- Getting Expressive: Digging deep into Expression Trees Part 1
- Getting Expressive: Digging Deep into Expression Trees Part 2
- Linq to SQL DataContext Lifetime Management
- Business Object wrapper around LINQ to SQL
- Visual WebGui and a LINQ to SQL quirk
- LINQ and Entity Framework Posts for 2/4/2008+
at
10:42 AM
0
comments
Posted by
roni schuetz
Saturday, November 01, 2008
Using Panel.DefaultButton property with LinkButton control in ASP.NET
ASP.NET has great limitation — only one server form on the page. Even if you are developing complex page, which looks like several forms with different submit buttons, in fact you have only one form. So we have a problem: How browser understanding which button should be triggered when user pressed ENTER? It uses first Button control (usually that’s wrong), and if you have LinkButton’s, they would never be triggered. In ASP.NET 2.0 new property has been added to the Panel and HtmlForm controls — DefaultButton, which can be used to specify ID of the control, which implements IButtonControl interface (usually Button and LinkButton). This button control would be triggered when user pressed ENTER. But there is one big problem exist: LinkButton control would not be triggered in Firefox on ENTER. In this article I will show why this problem take place and how to solve.
Read the solution at Dmytro's Blog: Using Panel.DefaultButton property with LinkButton control in ASP.NET
at
1:18 PM
0
comments
Posted by
roni schuetz
Saturday, October 11, 2008
Evaldas Jocys: Globalization Resources for Multilanguage Development
http://www.codeproject.com/KB/locale/JocysComGlobalization.aspx?msg=2760744#xx2760744xx
Introduction
This article contains MUST HAVE tables and data for proper multi language development. I highly recommend to use ISO (International Organizations for Standardization) as primary source of information, because this is the only way to go for high quality products and compatibility. Please remember that ISO usually only manages standards. Behind each ISO standard there are companies which supplies databases and updates to commercial users. Internet is also good source of information so I've collected globalization data from various resources and placed into 6 tables. If you have some suggestions then please contact me by email: Evaldas Jocys <evaldas@jocys.com>
Data for these tables are required to produce full multilingual support:
- Languages - information about all languages.
- Cultures - information about all cultures (Language + Country).
- Encodings - information about all encodings.
- Ranges - can help to get customer's culture by IP.
- Currencies - business information about each country.
- Currencies by Country- currencies used in country.
it would be very intersting to combine this with the following:
ASP.NET 2.0 Custom SQL Server Resource
ProviderBy Jeff Modzel
at
5:25 PM
0
comments
Posted by
roni schuetz
Friday, October 10, 2008
Trivia - Chaostriva.com
do you like trivia? well I do and found finally a multiplayer trivia game - try this out: http://www.chaostrivia.com/
enjoy and lets play
would be funny to create a quiz about .net, web or anything related to development.
at
10:55 PM
0
comments
Posted by
roni schuetz
Labels: links
dictonary serializable
after some researches how to serialize dictonary in .net I found the following solutions:
only XML serialization: http://weblogs.asp.net/pwelter34/archive/2006/05/03/444961.aspx
inclusive Binary serialization: http://blogs.microsoft.co.il/blogs/applisec/archive/2008/02/23/serializable-dictionary.aspx
at
10:17 AM
0
comments
Posted by
roni schuetz
Labels: .net, C#, links, SharedCache
Wednesday, September 10, 2008
New Personal Website
I uploaded a new website, let me know what you think about: http://www.ronischuetz.com
at
10:35 PM
0
comments
Posted by
roni schuetz
Labels: links
LogParser SQL Statemts for IIS Log files
I uploaded some LogParser SQL Statements for IIS Log files.
- http://www.ronischuetz.com/code/AverageResponseTimePerHour.html
- http://www.ronischuetz.com/code/Hit_Frequency.html
- http://www.ronischuetz.com/code/NetworkAnalysis.html
- http://www.ronischuetz.com/code/RequestsPerHour.html
- http://www.ronischuetz.com/code/RequestsPerMin.html
- http://www.ronischuetz.com/code/RequestsPerMin_WebSites.html
- http://www.ronischuetz.com/code/ResponseTime.html
- http://www.ronischuetz.com/code/Top50LongestRequest.html
- http://www.ronischuetz.com/code/unique_clients.html
- http://www.ronischuetz.com/code/uniqueClientsPerHour1.html
- http://www.ronischuetz.com/code/uniqueClientsPerHour2.html
with a simple batch job you able to execute all queries at once:
Download: http://www.ronischuetz.com/code/LogParserSqlScripts.zip
at
10:31 PM
0
comments
Posted by
roni schuetz
The Difference Between Piping and Polling
Jeff Standen explains about "The Difference Between Piping and Polling"
Piping (a.k.a. Pushing)
With the piping method, e-mail is delivered to an application in real-time at the cost of server resources and redundant application overhead.
Pros:
It’s fast. E-mail is delivered to the helpdesk proactively and in real-time.
It’s modular. The relatively expensive operations required to convert a raw MIME e-mail message into plaintext with usable file attachments can be offloaded to a speedy, specialized application. In previous versions of Cerberus Helpdesk, e-mail processing was handled by a parser written in the “C” programming language.
Cons:
It doesn’t scale well. Each new message is processed concurrently, each costing the overhead of the application starting up, initializing resources, processing, and then shutting down between each handled message.
It can bounce/blackhole messages. Since mail is delivered in real-time, the mail server is generally looking for an immediate clear-cut success or failure response code from an application. That means if you’re upgrading, tweaking, rebooting, or otherwise taking your helpdesk offline for a few minutes, new mail is bouncing for later retry. That’s normal behavior. However, if your helpdesk is accessible but in a broken state (e.g. halfway through an upgrade, having database issues) then it’s possible for mail to be accepted but not processed.
at
2:19 PM
0
comments
Posted by
roni schuetz
Labels: links
Friday, August 29, 2008
LINQ to SQL Serialization
Use the Generics, Extension and Reflection features to implement a generic serialization class library for LINQ to SQL classes
http://www.west-wind.com/WebLog/posts/147218.aspx
http://sql.codeproject.com/KB/linq/linqsqlserialization.aspx
at
4:00 AM
0
comments
Posted by
roni schuetz
Labels: links
Tuesday, August 26, 2008
Build a Web Chat Application using ASP.Net 3.5, LINQ and AJAX (in C# 3.5)
Junnark Vicencio explains how to build a chat application within 2 hours.
Technologies Used: ASP.Net 3.5, AJAX, JavaScript, C# 3.5, LINQ-to-SQL, MS SQL Server 2000/2005
http://www.junnark.com/Articles/Build-a-Web-Chat-Application-Using-ASP-Net-LINQ-and-AJAX-CS.aspx
at
11:10 PM
0
comments
Posted by
roni schuetz
Friday, July 18, 2008
Improve Web Application Performance
Introduction
In the IT world, software applications are being rapidly developed. Clients, and so employers, are just looking for those teams/individuals who can build up applications rapidly, just bothering to make their application live; but what often happens after an application goes live is that users start to use the application and it doesn’t respond well. At this point, clients start to lose users and business.To code an application is not a big deal; I believe it can be done by virtually anyone, meaning it is not necessary to have great knowledge or experience. Improving performance of an existing application (especially an one put together rapidly) could be quite risky and could cause many ripple effects. Things must be planned first to avoid horrible results.The following are a few points that can make a site scalable and reliable; but which may initially slow down development. I believe that overall, when maintenance and future changes are taken into account, total development time would be reduced.
1. Minimize HTTP based Requests
2. HTTP Compression:
3. Correct Formatted Images at the Right Place:
4. Compress CSS, JavaScript and Images
5. CSS at Top
6. Javascript at Bottom
7. Content Delivery Network: (CDN)
8. Ajax
9. Ajax vs. Callback
10. Reduce Cookie size
11. Use Cache appropriately
12. Upload compiled code rather than source code
Following are few good practices to gain better performance:
- For HTTP compression, GZip is considered the most effective and most popular by means of browsers and HTTP server. It can reduce file size up to 70% in size.
- Always keep JavaScript and CSS in external files.
- Avoid redirects until needed. Server.Transfer is also provided so consider that as well since it performs better in some conditions.
- Minimize use of Iframes as it's costly.
- Avoid try-catch blocks for control-flow as they perform poorly. Exceptions should be used only in truly exceptional situations.
- Minimize Cookie/CSS sizes.
- Minimize DOM objects on page as they are heavy weight.
- Use link tags rather than @import to use/link up CSS.
- Favicon, being a static image displayed in the browser’s address bar, should be cacheable and compressed.
- Always prefer a cache-friendly folder structure. For example, create specific folders for static contents, like /static for static images/static pages.
- SSL can never be cached so minimize its usage. Keep it for those pages which need to be secure, rather than using it for all the pages.
- HTTP Post requests can’t be cached, so choose the HTTP method appropriately.
- Prevent Denial of Service (Dos) attacks.
- Prevent SQL Injection.
- Prevent Cross Site Scripting (XSS).
Read the full article by dr.honey (IT SURGEON) at the following link: http://developerscon.blogspot.com/2008/06/improve-web-application-performance.html
at
9:16 PM
0
comments
Posted by
roni schuetz
Labels: .net, cache, Database, java script, links, network, performance
Understanding Object Pooling in Microsoft .NET
Joydip Kanjilal has published a very intersting object pooling article.
Introduction
Object Pooling is nothing new. It is a concept that implies that we can store a pool of objects in memory to be reused later and, hence, reduce the load of object creation to a great extent. An Object Pool, also known as a Resource Pool, is a list/set of ready to be used reusable objects that reduce the overhead of creating each object from the scratch whenever a request for an object creation comes in. This is somewhat similar to the functioning of a Connection Pool, but with some distinct differences. This article throws light on this concept (Object Pooling) and discusses how we can implement a simple generic Object Pool in .NET.
What is an Object Pool?
An Object Pool may be defined as a container of objects that are ready for use. Lists of ready-to-be-used objects are contained in this pool. Whenever a new request for an object creation comes in, the request is served by allocating an object from the pool. Therefore, it reduces the overhead of creating and re-creating objects each time an object creation is required. "An object pool is an object that holds a list of other objects, ready to make them available for use (to yet another object, probably). It does the management work involved, like keeping track of which objects are currently in use, how many objects the pool holds, whether this number should be increased."
Why is an Object Pool required?
The biggest advantage of using Object Pooling is that it minimizes the consumption of memory and the system's resources by recycling and re-using objects as and when it is needed and serving the request for new objects from the pool of ready-to-be-used objects. The objects that the application is done with (the objects are no longer needed) are sent back to the pool rather than destroying them from the memory. According to MSDN, "Once an application is up and running, memory utilization is affected by the number and size of objects the system requires. Object pooling reduces the number of allocations, and therefore the number of garbage collections, required by an application. Pooling is quite simple: an object is reused instead of allowing it to be reclaimed by the garbage collector. Objects are stored in some type of list or array called the pool, and handed out to the client on request. This is especially useful when an instance of an object is repeatedly used, or if the object has an expensive initialization aspect to its construction such that it's better to reuse an existing instance than to dispose of an existing one and to create a completely new one from scratch."
read the full article at the following link: http://www.dotnetjohn.com/articles.aspx?articleid=252
at
9:12 PM
0
comments
Posted by
roni schuetz
Wednesday, July 16, 2008
Debugging ASP.NET on a Production Server 101
Very good information about Debugging can be found at the following article: Debugging ASP.NET on a Production Server 101
at
10:52 AM
0
comments
Posted by
roni schuetz
Wednesday, January 16, 2008
Text File does not get deployed from Class Library Project into Asp.NET Web Application
The issue sounds simple to me:
Text File does not get deployed from Class Library Project into Asp.NET Web Application
"We have a webproject and would like to deploy HTML and
Text Templates from a common Project into the web project
output folder.
The Attributes on the text / html files are set like this:
Build Action: Content
Copy to Output Directory: Copy Always
it just copy the files into the common csharp project under the bin/debug
but it doesn't appears within the web project.
any idea how to solve this issue without a lot of post build scripts?"
This have been posted 2 days ago I posted the following problem at: http://forums.asp.net/t/1205184.aspx
To fix this issue you simply need to think in different direction - the oposite one :-)
Step 1: Don't add your files you would like to share in TFS (Team Foundation Server) into your Class Library Project - add files (html / xml / text / etc.) into your App_Data folder in your Asp.NET Web Application Project Type.
Step 2: Create your Folder within your Class Library Project you like to have the files. Once you have created the folder, you can right click on the folder and select : Add -> Existing Item
This will open you a dialog folder with a small HINT which is the BIG SHOOT for this issues. Don't simply add it while you press "Add" you need to select the small arrow near the Button and select "Add As Link" like the below printscreen shows:
Once you have done above steps, select your file and look at the file properties within your Visiual Studio. There you find some Attributes you need to check, you should check that the "Build Action:" is equal to "Content" and the "Copy to Output Directory:" is set to "Copy Always" or "Copy if newer".
In my case I do not need now to held the files redunded and sync them upon changes ....
just think different you will solve the problem!! was the motto upon this issue !
at
3:30 PM
2
comments
Posted by
roni schuetz


