Jay Nathan's Weblog
Thursday, May 27, 2004
Random Observation #3
.NET Configuration Files
Microsoft .NET configuration files differ with the type of application you are developing. If we are dealing with ASP.NET, the configuration file is called "web.config" and will reside in the root of the virtual directory where your application lives.
For executable applications, though, we use the app.config file. There is no configuration file option for class libraries (dll's). If you need to load configuration items into a class library at run time, they must be loaded from the executing assembly's (exe) configuration file. When you compile an executable project that contains an "app.config" file, you will notice that a copy of that file is placed in the same directory that the executable saved to, but with a different name: <app_name>.exe.config. From run time, reflection is used to retrieve the proper configuration file from the APPBASE directory. Since configuration files are named after the executables that they configure, you can have multiple executables in one directory, all with their own configuration files which you couldn't do by default if the configuration filename was left as app.config.
Wednesday, May 26, 2004
I'm trying to get some stuff wrapped up so that I can get out a little early the next couple of days and to relax over the Memorial Day weekend. Right now, my main focus is on getting a Reporting Services catalog browser web part to talk to a Report Viewer Web Part correctly. Somewhere between the many layers of ASP.NET and WebPartPage framework that I am building upon, my code isn't executing in the order that I need ti to ;(
When I get this knocked out, I'll almost have my milestones for the week met. I hope to begin posting some samples from my work here very soon.
Tuesday, May 25, 2004
Reporting Services/SharePoint Integration
I'm working on integrating some Reporting Services functionality into SharePoint and will be posting some of findings and best practices techniques in the coming days/weeks.
Both Reporting Services and SharePoint offer an extensible framework that developers can extend which offer a world of opportunity. The combination of the two frameworks could provide an infrastructure for security and reporting that every custom developed application requires. So in theory, these frameworks could become the platform upon which to build future custom applications. Of course, licensing, performance, and scalability questions may arise, but these frameworks provide options for scalability and performance out of the box. So that just leaves licensing...
Reinstalling Reporting Services
I've somehow hosed Reporting Services on my server so that whenever I try to access any report (and only reports, not data sources or folders) through Report Manager I get a "You are not authorized to view this page" error in the iframe that would normall display the report. I check the permissions on the directories and ensured that IIS had the proper settings for the Reports and ReportServer v-directories...
I opted for a quick reinstall... If anyone has seen this before, I'd like to know how you fixed it.
Monday, May 24, 2004
Details about my setup
I've set up my weblog on Blogger.com and then created an account on FeedBurner.com to publish my feed in RSS 2.0. For some reason, FeedBurner's SmartFeed feature wasn't working for me. So, tired of dealing with it, I used the Convert Format Burner to publish in RSS. Now that I'm all set up, I'm going to start looking for a good Windows client piece to actually do my posting from (rather than having to visit Blogger.com).
UPDATE: I turned the Convert Format Burner (to RSS 2.0) off on FeedBurner. I would have had to update the feed each time I posted to my blog and obviously that wasn't an option. For my blog client, I am using w.bloggar.
At last, I've got my very own weblog up and running!
My name is Jay Nathan and I am a Senior Consultant at MARINER. We are based out of Charlotte, NC and develop analytical and collaborative solutions (as well as the occasional custom application) for our clients. We use a customized process called Ocracoke which is based upon RUP to manage our projects. Before coming to Mariner, I worked with Microsoft's .NET technologies for about 2 and a half years, and have been able to bring a lot of that expertise to bear in my new position. We are currently doing work with customizing and integrating Windows SharePoint Services (and Portal Server) and SQL Server Reporting Services which are all based on .NET technologies. When developing custom pieces of software called Web Parts for SharePoint, having a solid understanding of ASP.NET is imperative.
So enough rambling... In the future, look for musings on .NET related topics here, including a good bit of content revolving around SharePoint, Reporting Services and other framework technologies that Microsoft is producing. I'll probably throw some personal stuff in as well!