April 3, 2008 at 13:11 · Filed under Duyuru
The Microsoft Sharepoint Conference 2008 Istanbul is the third and final of three global SharePoint conferences, following Seattle and Dubai.
This world-class, two-day conference, to be held at the Swissotel, Istanbul from April 10-11, will showcase the lates innovations, features and functionality for the 2007 SharePoint prodcuts and technologies.
The Microsoft SharePoint Conference 2008 Istanbul will provide an unprecedented opportunity for customers and partners in the region to meet and network with Office System product teams, fellow IT professionals, and partners.
The sessions will be delivered by Product Managers coming from the Product Group, MVPs, Partners and specialists from the Istanbul Office.
Speakers
The sessions will be delivered by Product Managers coming from the Product Group, MVPs, Partners and specialists from the Istanbul Office.
Joel Oleson : SharePoint Senior Technical Product Manager
Jerome Thiebaud : SharePoint Designer Product Manager
Joseph Khalaf : SharePoint Global Support Engineer
Todd Klindt : Windows Sharepoint Services MVP, TechNet Magazine Writer
Patrick Beeharry : Office Servers Product Manager, Microsoft MEA
Who are the Target Audience for SharePoint Conference 2008- Istanbul?
The session content is targeted at IT Professionals and Architects. Seasoned SharePoint professionals as well as people that are new to SharePoint Products and Technologies will all learn something new! The content theme this year is “Real world guidance and experience”, we have top notch speakers lined up from Microsoft, our customers, our Partners and the MVP technical community all geared up to share their knowledge.
To register for the event:
http://www.sharepointconferenceistanbul.com/en/register/Pages/default.aspx
March 17, 2008 at 12:29 · Filed under Asp.NET 2.0, Asp.NET 3.5, Know how - Workaround
In case you get the following exception while trying to run an ASP.NET application, the solution is not as simple as setting the "enableEventValidation" configuration to "false" all the time.
Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
I had such a problem last week. One of my colleagues asked me to check a problem because he could not see it and everything used to work perfectly before. I must confess that I spent hours to find the problem. Even if I set the "enableEventValidation" value to "false", nothing worked and everything started to lose its ViewState data.
Finally, I’ve found that the problem was a forgotten "form" tag within a user control. So, if you have such a problem about losing ViewState unexpectedly and exceptions about Event Validation, double check your code not to have such <form> tags.
February 25, 2008 at 14:27 · Filed under HTML
We have been using HTML 4.01 and XHTML 1.0 for a long time. And the draft of HTML 5 was published a month ago. There are several new tags that I suppose you will like. For example <input type="number" /> will show up an input control that your visitor may only enter some numeric value. That sounds really cool! You may read a short list of changes/improvements below but that is not the complete list for sure.
The following elements have been introduced for better structure:
section represents a generic document or application section. It can be used together with h1-h6 to indicate the document structure.
article represents an independent piece of content of a document, such as a blog entry or newspaper article.
aside represents a piece of content that is only slightly related to the rest of the page.
header represents the header of a section.
footer represents a footer for a section and can contain information about the author, copyright information, et cetera.
nav represents a section of the document intended for navigation.
dialog can be used to mark up a conversation like this:
<dialog>
<dt> Costello
<dd> Look, you gotta first baseman?
<dt> Abbott
<dd> Certainly.
<dt> Costello
<dd> Who's playing first?
<dt> Abbott
<dd> That's right.
<dt> Costello
<dd> When you pay off the first baseman every month, who gets the money?
<dt> Abbott
<dd> Every dollar of it.
</dialog>
figure can be used to associate a caption together with some embedded content, such as a graphic or video:
<figure>
<video src=ogg>…</video>
<legend>Example</legend>
</figure>
Then there are several other new elements:
audio and video for multimedia content. Both provide an API so application authors can script their own user interface, but there is also a way to trigger a user interface provided by the user agent. source elements are used together with these elements if there are multiple streams available of different types.
embed is used for plugin content.
m represents a run of marked text.
meter represents a measurement, such as disk usage.
time represents a date and/or time.
canvas is used for rendering dynamic bitmap graphics on the fly, such as graphs, games, et cetera.
command represents a command the user can invoke.
datagrid represents an interactive representation of a tree list or tabular data.
details represents additional information or controls which the user can obtain on demand.
datalist together with the a new list attribute for input is used to make comboboxes:
<input list=browsers>
<datalist id=browsers>
<option value="Safari">
<option value="Internet Explorer">
<option value="Opera">
<option value="Firefox">
</datalist>
The datatemplate, rule, and nest elements provide a templating mechanism for HTML.
event-source is used to "catch" server sent events.
output represents some type of output, such as from a calculation done through scripting.
progress represents a completion of a task, such as downloading or when performing a series of expensive operations.
The input element’s type attribute now has the following new values:
datetime datetime-local date month week time number range email url
The idea of these new types is that the user agent can provide the user interface, such as a calendar date picker or integration with the user’s address book and submit a defined format to the server. It gives the user a better experience as his input is checked before sending it to the server meaning there is less time to wait for feedback.
And of course there are new attributes and changes within the currently existing attributes.
HTML 5 has introduced several new attributes to various elements that were already part of HTML 4:
The a and area elements now have a media attribute for consistency with the link element. It is purely advisory.
The a and area elements have a new attribute called ping that specifies a space separated list of URIs which have to be pinged when the hyperlink is followed. Currently user tracking is mostly done through redirects. This attribute allows the user agent to inform users which URIs are going to be pinged as well as giving privacy-conscious users a way to turn it off.
The area element, for consistency, now has the hreflang and rel attributes.
The base element can now have a target attribute as well mainly for consistency with the a element and because it was already widely supported. Also, the target attribute for the a and area elements is no longer deprecated, as it is useful in Web applications, for example in conjunction with iframe.
The value attribute for the li element is no longer deprecated as it is not presentational. The same goes for the start attribute of the ol element.
The meta element has a charset attribute now as this was already supported and provides a nicer way to specify the character encoding for the document.
A new autofocus attribute can be specified on the input (except when the type attribute is hidden), select, textarea and button elements. It provides a declarative way to focus a form control during page load. Using this feature should enhance the user experience as the user can turn it off if he does not like it, for instance.
The new form attribute for input, output, select, textarea, button and fieldset elements allows for controls to be associated with more than a single form.
The input, button and form elements have a new replace attribute which affects what will be done with the document after a form has been submitted.
The form and select elements (as well as the datalist element) have a data attribute that allows for automatically prefilling of form controls, in case of form, or the form control, in case of select and datalist, with data from the server.
The new required attribute applies to input (except when the type attribute is hidden, image or some button type such as submit) and textarea. It indicates that the user has to fill in a value in order to submit the form.
The input and textarea elements have a new attribute called inputmode which gives a hint to the user interface as to what kind of input is expected.
You can now disable an entire fieldset by using the disabled attribute on it. This was not possible before.
The input element has several new attributes to specify constraints: autocomplete, min, max, pattern and step. As mentioned before it also has a new list attribute which can be used together with the datalist and select element.
input and button also have a new template attribute which can be used for repetition templates.
The menu element has three new attributes: type, label and autosubmit. They allow the element to transform into a menu as found in typical user interfaces as well as providing for context menus in conjunction with the global contextmenu attribute.
The style element has a new scoped attribute which can be used to enable scoped style sheets. Style rules within such a style element only apply to the local tree.
The script element has a new attribute called async that influences script loading and execution.
The html element has a new attribute called manifest that points to an application cache manifest used in conjunction with the API for offline Web applications.
Several attributes from HTML 4 now apply to all elements. These are called global attributes: class, dir, id, lang, tabindex and title.
There are also several new global attributes:
The contenteditable attribute indicates that the element is an editable area. The user can change the contents of the element and manipulate the markup. The contextmenu attribute can be used to point to a context menu provided by the author. The draggable attribute can be used together with the new drag & drop API. The irrelevant attribute indicates that an element is not yet, or is no longer, relevant. </LI>
The following are the attributes for the repetition model. These are global attributes and as such may be used on all HTML elements, or on any element in any other namespace, with the attributes being in the http://www.w3.org/1999/xhtml namespace.:
repeat repeat-start repeat-min repeat-max
HTML 5 also makes all event handler attributes from HTML 4 that take the form onevent-name global attributes and adds several new event handler attributes for new events it defines, such as the onmessage attribute which can be used together with the new event-source element and the cross-document messaging API.
If you are interested of reading the differences between HTML 4.01 and HTML 5, you may visit http://www.w3.org/TR/html5-diff/.
February 12, 2008 at 16:11 · Filed under Duyuru, Visual Studio 2008
I have been testing this hotfix for a while and it is publicly available now. If you are using either Visual Studio 2008 or Visual Web Developer (or both) to develop your web applications, I extremely suggest you downloading and installing this hotfix.
A quote from Visual Web Developer Team’s blog about the fix list is below.
HTML Source view performance
Source editor freezes for a few seconds when typing in a page with a custom control that has more than two levels of sub-properties. “View Code” right-click context menu command takes a long time to appear with web application projects. Visual Studio has very slow behavior when opening large HTML documents. Visual Studio has responsiveness issues when working with big HTML files with certain markup. The Tab/Shift-Tab (Indent/Un-indent) operation is slow with large HTML selections.
Design view performance
Slow typing in design view with certain page markup configurations.
HTML editing
Quotes are not inserted after Class or CssClass attribute even when the option is enabled. Visual Studio crashes when ServiceReference element points back to the current web page.
JavaScript editing
When opening a JavaScript file, colorization of the client script is sometimes delayed several seconds. JavaScript Intellisense does not work if an empty string property is encountered before the current line of editing.
Web Site build performance
Build is very slow when Bin folder contains large number of assemblies and .refresh files with web-site projects.
Click here to download the hotfix.
Click here to read more about installing and uninstalling the hotfix.
February 1, 2008 at 12:28 · Filed under Training and Seminars
I had a chance to train some students from Microsoft Student Partners program yesterday. The training included some headlines from ASP.NET, AJAX and new features in Visual Studio 2008. The bowling party afterwards the training was fun.
Thanks Mehmet Emre from Microsoft Turkey for the opportunity.
I will attach some pictures from the bowling party once I have them.
January 25, 2008 at 15:34 · Filed under Open Source, Windows Live Writer
I felt like developing my first Live Writer plugin last night then I checked this page to see if someone requests any useful plug-in that I would like to spend my time developer. There were a few ideas about <pre> tag. I thought that it was a good idea to develop such a plugin to insert any tag snippet at anytime because I also need <code> and <pre> tags to share code parts on my blog.
I used an XML file as the data store so it might be a good sample of you seeing how to store settings data of your own plugin.
If you need to see how to develop a Live Writer plugin using C#, you can see its code on CodePlex: http://www.codeplex.com/InsertTagSnippet
If you just want to download and install the plugin, you can do that here: http://gallery.live.com/liveItemDetail.aspx?li=[…]
January 24, 2008 at 18:01 · Filed under Genel
Martin has told me a lot about Windows Live Writer and I wanted to give it a try. The UI looks perfect, it supports a lot of blog types and most importantly, it doesn’t need you to make a lot of experimental settings.
What I did to set it up was just writing my blog’s URL, username and password. I could not believe that it was all!
You can click the screen shot of the UI above to see the bigger version of it so you can have an idea what it really looks like.
When you look at the screen shot, you will see that it is not just a basic Rich Text Editor replacement of your blog’s admin panel. It download the CSS files that your blog uses and you write your post like you are editing the content directly on the post page.
January 23, 2008 at 02:32 · Filed under Genel
This is not a recent news, Visual Web Developer 2008 Express Edition and Visual C# 2008 Express Editions have been available for download for a long time and as you know, they are for FREE. I just wanted to confirm that all my visitors are aware of this news.
Product links:
January 23, 2008 at 01:01 · Filed under Asp.NET 1.1 - 2.0, Asp.NET 3.5
If you need to divide the web.config or app.config file into pieces for any reason - imagine you just don’t like a lot of settings of components that you will never need to change - it is even possible in .NET. The only thing you have to find out is how to use “ConfigSource” property of System.Configuration.SectionInformation (MSDN: Contains metadata about an individual section within the configuration hierarchy.) class.
Each configuration section that derives from this class has the ability of getting its configuration settings from a separate “config” file.
In a case that you would like to store your connections strings in a different “config” file, the way you have to follow is shown in the example below.
web.config file:
<?xml version="1.0"?>
<configuration>
<connectionStrings configSource="ConnectionStrings.config" />
<system.web>
<!-- settings... -->
</system.web>
</configuration>
ConnectionStrings.config file:
<connectionStrings>
<clear />
<add name="SqlServer" connectionString="..." />
</connectionStrings>
January 18, 2008 at 14:49 · Filed under .NET Framework 3.5, Visual Studio 2008
I know that we all have been waiting for this great news for a long time. Now you can download symbols for .NET Framework source code and you can see or even debug the framework’s itself.
ScottGu has a long post describing how you can access this feature in Visual Studio 2008.
This is what he says:
Last October I blogged about our plan to release the source code to the .NET Framework libraries, and enable debugging support of them with Visual Studio 2008. Today I’m happy to announce that this is now available for everyone to use. Specifically, you can now browse and debug the source code for the following .NET Framework libraries:
.NET Base Class Libraries (including System, System.CodeDom, System.Collections, System.ComponentModel, System.Diagnostics, System.Drawing, System.Globalization, System.IO, System.Net, System.Reflection, System.Runtime, System.Security, System.Text, System.Threading, etc).
ASP.NET (System.Web, System.Web.Extensions)
Windows Forms (System.Windows.Forms)
Windows Presentation Foundation (System.Windows)
ADO.NET and XML (System.Data and System.Xml)
We are in the process of adding additional framework libraries (including LINQ, WCF and Workflow) to the above list. I’ll blog details on them as they become available in the weeks and months ahead.
To read the rest of the post, please follow this page.
Next entries »
