Things I have noted during the Techday 2011 @ Metropolis Antwerp.. Just my personal thoughts. There will be mistakes, as several things are new for me :-)

1. Things I will remember -my notes- Alexander Vanwynsberghe

2. About TechDays 2011 When? 26 – 27 – 28 April Where? What? 3-day conference About learning new products Rediscovering existing technologies Who? IT Professionals and Developers from every sector. 2 days main conferences 1 day technical Deep Dives About? We have IT in our DNA and are happy to share it!

3. Tuesday April 26th Day 1

5. ASP.NET MVC3

6. OSS

7. NuGet packages

8. Modernizr: html5

9. Html5 markup

10. Expression web superpreview

11. Different browser layout comparison

12. Glimpse

13. Looks like Firebug but in jQuery

14. Debugging server side

15. RoutingPieces snap together

17. Hosted on Windows Azure (cloud)

18. 300-work hours

19. +150 hours design

20. WP7 application in Silverlight

21. Using RIA services

22. Web based front-end for regular browsers

23. MVC3

24. Data retrieval with Odata

25. MVC3 + Odata = no data save -> wrapper

26. jQuery mobile for mobile browsers

27. Based on clean, semantic HTML

29. Authentication

30. Cookie container

31. Custom view-engine for mobile

32. 3 weeks, 4 servers < 500€

33. Azure web publish on deploy

34. 30 seconds <> 20 minutes

35. Only use in DEV

36. SQL Azure throttling

37. Throttle connections to protect resources in the data center

38. Manifested by a dropped connection

40. Using http

41. Return ATOM or JSON

42. Queryable from browser

43. http://site/Category(1)/Products?$top=2&$orderby=name

44. WCF service

45. REST-based data service

46. Make data exposable for other systems/devices

47. Query navigation, links to navigate

49. Use HTTP as an application layer protocol

50. Using MediaTypeProcessor

51. Return data types

52. http://site/contact/profile => .pngimage

53. HTTP Messages

55. Difference in mouse events

56. Mouse = finger

57. Slide events

58. Pitch events

59. Zooming

60. Tombstoning

61. Session restore when app is closed

62. Save off state data

63. Using Isolated Storage

65. Extreme programming -> TDD

66. Many teams using ‘SCRUM_BUT’

67. Sprints are time boxed

68. Product backlog = dynamic

69. Sprint planning 2-8 hours

70. Standup max 15 min, NO exceptions

71. After sprint -> sprint retrospective = Like Wall

72. Stimulate: pizza’s, m&m machine..

73. Test NOT only on the end

76. Third party libraries into a .NET application

77. Command line & GUI

78. .nupkg can be opened to explore its dependencies

79. Automatic web.config changes on adding package

80. Demo Elmah (error logger)

81. Demo command line creation of a .nupkgfile

82. A package with assembly numbers etc.

83. Local NuGet server

85. Modernizr to detect features (JavaScript)

86. Semantic markup

87. Contains offline storage database

88. Used for offline ‘applications’

89. SVG integration

90. Used for drawings

91. Games & Animations

92. Good animation is 60fps = window.setinterval(17)

93. <video>, <audio>, and <canvas> elements

94. Internet Explorer 10 is even faster than IE9

96. User interface testing

97. Silverlight, WinForms, Web

98. Can be created manual, or converted from MTM test

99. Possibility to check control values

100. For web applications: Controls are found using DOM search

101. The position of clicking is also important

102. Resizing independent

103. Integrates in TFS build

105. Higher-level Platform-as-a-Service (PaaS)

106. Supports several languages (.NET, Java, Ruby, PHP)

107. Access Control Service (Facebook, Google, AD)

108. Service Bus (connections between applications)

109. Application caching

111. Implements model-view-controller pattern

112. Razor server side template engine

113. HTML 5 enabled project templates

114. Unobtrusive JavaScript validators (properly wrapped)

115. Integrating with Dependency Injection or Inversion of Control (IOC) containers

116. Sessionless Controller Support

119. TFS will run on azure -> 20 sec set-up time

120. Microsoft uses TFS with 17TB data

121. Changes can be drag’n dropped for merging

122. Dependency graph support (feature pack 1)

123. Possibility to check architecture in TFS build

124. TFS web access = SharePoint with web parts

125. Integration with Microsoft projects

127. How to reproduce?

128. Lack of visibility into the action

129. Environment difference

130. Ping pong between devs & testers

131. Build-deploy-test cycle

132. Use clean environment

133. Using Hyper-V snapshots

134. Client -> Hyper V-host -> VM with test environment

135. Template has 3 agents:

136. test-agent/build-agent/lab-agent

137. Integrated in MTM 2010 using lab-management

138. Integrated in TFS using build process template

139. Web deployment

141. Kanban

142. Make visible

143. Limit work in progress

144. Help the workflow

145. It is quantitatively managed

146. Lead time

147. Cycle time

148. Predictability

149. Efficiency

150. Share resources on a WIP overload of a person

151. Less structured than Scrum

152. Work In Progress (WIP) Limits are change agents

154. Breakpoints

155. Conditional breakpoints

156. Fast processing breakpoints in loops

157. Local watch re-naming

158. Crash-dump log files

159. IntelliTrace

160. Breakpoint export & import

162. Added to source control

163. Generate SQL scripts for deployment

164. Incremental deployment

165. Integration in TFS build

166. Data generation possibility