If you have a model object with a property named Id , you may have run into an issue where your model state is invalid when binding to that model even though you don’t have an “Id” field in your form. The following scenario should clear up what I mean Read More......(read more)
We are experiencing one odd issue in our development server, web deployment project build fails but the there are no errors in visual studio's errors list, and the output shows only:
Done building project "XXXX.csproj_deploy.wdproj".
========== Rebuild All: 6 succeeded, 1 failed, 0 skipped ==========
There seem to be other reports of the same issue. The workaround that seems to work is compiling from command line with msbuild /p:Configuration=Release path\XXXX.csproj_deploy.wdproj
In this way the project builds successfully, but is still not a solution.
Has anyone experienced something similar? Any other workaround you know about?
Donn Felker has a great post that explains the different uses of LINQ's ToLookup and ToDictionary. Check it out!
What happens when you need to protect your whole site so that only Authenticated users can access our site. Since I received this question twice this week I thought I’d share a tip. To allow ONLY authenticated access to your site using Forms authentication Read More......(read more)
As my object to object mapper is now almost completed and I am sure it is good idea to stay on LCG (Lightweight Code Generation) I can now compare the performance of my mapper to AutoMapper.
NB! If you are building applications that will run on public servers then use AutoMapper as it is widely used and tested. AutoMapper has tons of features that my little mapper doesn’t have. Also it is easier to get support for AutoMapper if you face the troubles.
Okay, but let’s compare results. Because my mapper has no powerful features and is therefore very light it performs a little bit faster. Take look at the following report.
~6 times faster - not bad at all for my little feature-free mapper or what do you think?
There are some improvements I plan to add to my mapper but as these improvements doesn’t affect copying operation. I will write my final version of mapper in near future and provide it in this blog as binary and Visual Studio 2008 project.
 |
[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu ] We shipped the VS 2010 RC on Monday , and have seen some great feedback regarding performance and stability with it. One issue Read More......(read more)
[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu]
We shipped the VS 2010 RC on Monday, and have seen some great feedback regarding performance and stability with it.
One issue, though, that we have seen a number of people run into is an intellisense crash that happens very frequently on machines that have UI Automation enabled and certain devices connected.
Crash Symptom
If you are encountering frequent VS 2010 crashes when you are typing in the editor while Intellisense is popping up and/or being dismissed then you are running into this issue.
Why does the crash happen?
The most common cause of the crash happening is that you are running a machine that:
- Is a Tablet PC (even if you aren’t using the pen)
- Has multi-touch screen drivers enabled
- Has an external input device like a pen or Wacom tablet
- Has a screen-reader enabled
It turns out that a late fix right before the RC shipped modified a UI input code path that unfortunately exposed this bug.
A patch is coming to fix this issue
We are working on shipping a VS 2010 RC patch that we’ll release next week that will fix the issue and prevent it from occurring. I’ll blog a pointer to the patch once it is available.
How to work around the issue now
There are two ways you can work around the issue now. One is to disable your Tablet services (read this article for details on how to do this) and/or disable Multi-touch/Pen drivers on your system. The other is to set a registry key.
You can read about both of these workaround in this VS Team Blog Post.
What if you still see crashes?
Please send me email (scottgu@microsoft.com) if you are still seeing any crashes after trying out these steps (or encounter crashes for non-Intellisense scenarios) – we’d like to make sure we investigate and follow-up any others you encounter.
Hope this helps,
Scott
David has posted about his experiences with F# and FsUnit.
Jonathan Cogley is the CEO of Thycotic Software, an agile software services and product development company based in Washington DC. Secret Server is our flagship enterprise password management product.
11 feb 2010: Virtual SharePoint 2010 Ignite Training for Developer
Day topics:
- Enterprise Content Management
- Extending SharePoint Search
- BI and Performance Point Services
- Sandboxed Solutions
Search
- Item-level security
- Control the resulting display URL
REST
- Access to SharePoint lists and library data
- …/_vti_bin/listdata.svc
- Lists and List items map to resources
- Listdata.svc/Employees(123)
BI Tools in SharePoint 2010
- Status Indicators
- Chart Web Parts
- PerfomancePoint Services
- Excel Services
- BI Search
- Visio Services
Videos:
Extending Search - The Connector Framework
Extending Search - Enhancing the Search UI
Extending Search - Creating Custom Ranking Models
Introducing Sandboxed Solutions
Estimados Amig@s:
En esta oportunidad quiero compartir con ustedes un screencast en donde explico la forma en que pueden administrar, de forma sencilla, las excepciones no controladas dentro de una aplicaciĂłn ASP.NET.
Es muy común encontrar, sea por desconocimiento o por mala práctica, aplicaciones ASP.NET que le presentan a un usuario final la famosa “Yellow Screen of death”, es decir aquella pantalla que para el usuario contiene un montón de caracteres en chino de los cuales no tiene idea de lo que se refiere.
Bien, arreglar este problema es muy sencillo, una simple configuración en el archivo Web.Config en donde se indica la página que se presentará en caso de excepciones o errores no controlados y listo.
El problema para nosotros los encargados del control, monitoreo y actualizaciĂłn de las aplicaciones, es que generalmente este tipo de errores nunca los recibiĂł, o bien si los recibimos, probablemente nos llega un print screen del error pero a veces se pierden algunos detalles.
Bien con el objetivo de facilitar el control, monitoreo y seguimiento de estos errores no controlados, les presentaré ELMAH (Error Logging Modules and Handlers), verán como a través de esta herramienta esta funcionalidad la podremos habilitar en nuestras aplicaciones, lo mejor de todo: SIN NECESIDAD DE MODIFICAR O AGREGAR CODIGO EN NUESTRA APLICACION:
ELMAH - Manejo de Excepciones No controladas en ASP.NET from Carlos Lone on Vimeo.
Espero este video les sea de mucha utilidad y que aprovechen esta poderosa herramienta.
Página principal del proyecto ELMAH: http://code.google.com/p/elmah/
Saludos,
Carlos A. Lone