I don't know of any reason offhand that you would have a problem with using this in an ASP.NET application. I am making heavy (read: killing me!) use of Flowplayer within my own project.
I can't really post a sample, as I have a ton of different configurations. But the simplest configuration I have would be something like (and this uses jQuery):
<script src="/js/jquery.min.js" type="text/javascript" charset="utf-8"></script>
<script src="/js/flowplayer.min.js" type="text/javascript" charset="utf-8"></script>
<script type="text/javascript" charset="utf-8">
$(window).load(function() {
$('.music-player').each(function() {
$f(this, {src: "/swf/flowplayer.commercial-3.1.5.swf", wmode: 'transparent'}, {
key: 'mykeywashereandIreplacedit',
clip: {
autoPlay: false,
autoBuffering: false
},
canvas: {backgroundColor: "#ffffff"}
plugins: {
audio: {url: '/swf/flowplayer.audio-3.1.2.swf'}
}
});
});
});
</script>
.music-player {
width: 400px;
height: 300px;
}
<a href="somefile.mp3" class="music-player"></a>
The key points being: make sure your Javascript files are included (I know that sounds asinine, but I've banged my head against the desk a dozen times before realizing that, due to permission errors or a typo a file wasn't being included on the page), make sure you have IDs/classes done right. In the example you posted, Kurt, make sure that .NET isn't actually replacing your anchor's ID with it's own generated ID. "player" is referring to the ID of the anchor, after all.
Hope I'm not being patronizing!