I upgraded Visual Studio 2010 from Beta to RC along with the .Net Framework 4.0 and oh my, I’m very impressed by the performance improvements. If you haven’t got it yet, here are the download links.
- Visual Studio 2010 Ultimate
- Visual Studio 2010 Premium
- Visual Studio 2010 Professional
- Visual Studio 2010 SDK
- Visual Studio Team Foundation Server
- .NET Framework 4
Happy Developing!
Ever since I discovered jQuery (that’s a couple of years ago) my life has been a joy ride when it comes to developing web apps. So I figured it’s only fair that I start writing about it. I would like to start with one of my favorite plug-ins written by Mike Alsup called Cycle. Among it’s numerous functionalities, I’d like to simply point out it’s ability to tick your tweets in the most basic form.
All you need to do is follow instructions from Twitter to retrieve your tweets using the RSS feed and put them in nested div containers in your page. Then call the following function to start ticking them.
$(function() {
$("div#twitter_feed").cycle('scrollUp');
})
Obvisouly, there’s so much more you can do with it. To get an idea of how this really looks like, take a look at Alsup’s page itself. You can also download the plugin along with some examples to get started.
Apart from working, watching college hoops and NFL games, I have no idea how time flies by so fast. Last week I was assigned to redo this “immoderate” InfoPath form that had no structure along with the lack of commendable functionality. This was my first InfoPath task, so though I’d share some nifty things I learned during the process.
1. ALWAYS create a well organized data source structure.
Because, if you want to change it later on, you are going to end up loosing existing data.
2. Getting the Current User in the local environment (for InfoPath Client)
3. Getting the Current User using Web Services (for InfoPath Web Forms i.e. SharePoint)
4. Getting custom code events to work on a web-based form
Go to Tools -> Form Options -> Security and Trust. Set the Trust Level to Full Trust.
5. Getting cascade drop-downs in a web-based form to populate secondary data source values.
Right-click on the primary drop-down box and select Properties. Go to the Browser forms tab and set Postback settings to Always.
6. Update existing form in SharePoint Library without having to create a new one.
Here, the trick is to create a unique file name for each form. You can use your own naming convention, but make sure to save the filename as a part of the data source. Create a new data connection to the Form Library and use the data field which contains the file name as the filename for the connection and make sure to select the “Allow overwrite if file exists” option. In the form, create an Update button and add a rule with the submit option that makes use of the data connection you just made. You’re done!
I got more, but they will have to wait till my next free tumblr time. :)
Had a hard time trying to find a download link to Management Studio (not express), so thought I’d just post them to help anyone else and myself in the future.
SSMS 32-bit: http://blogs.msdn.com/ssds/archive/2009/11/11/9921041.aspx
SSMS 64-bit: http://go.microsoft.com/fwlink/?LinkID=168735&clcid=0x409
SQL Server 2008 R2 CTP: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c772467d-e45b-43e1-9208-2c7b663d7ad1
Oh and btw, all the links are CTPs.
Have been trying to deploy this OLAP cube to Analysis Services using the Business Intelligence Development Studio. However, I ran into the following error multiple times.
OLE DB error: OLE DB or ODBC error: Login failed for user ‘SSAS_SVC_ACCOUNT’.; 28000.
Turns out that if you are using the Analysis Services service account to access the Data Warehouse (and deploy the cube), you need to grant (at least) read access to the service account for the Data Warehouse database in SQL Server.
For more information, check out the link below that addresses a similar issue.
Happy New Year Folks!! The long absence came from a combination of work overload, health download and the holiday pre/post-load period. let’s not get into details. it’s better that way.
Ushering 2010 also gave me the opportunity to deploy SharePoint 2010 and play around with some of the feature in the some-what buggy beta release. However, it looks and feels much better than MOSS 2007. I’m currently working on a BI project. New to the whole OLTP/OLAP stuff. More details coming soon..
With the recent release of Microsoft 2010 Betas it’s been quite the talk about making the leap to the 64-bit world. For SharePoint folks it’s also a question of compatibility. As of now, SharePoint 2010 Beta requires 64-bit SQL Server and either Windows Server 2008 or Windows 7. If you are running R2, then you are out of luck as Microsoft has not yet released a hotfix. Also, not to mention the escalated hardware requirements, specially memory-wise.
So if you wanna give it a try (myself included) here’s a nice write up by Jie Li that might come in handy with the planing and installation itself. Good Luck!
